From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Activating BMQ CPU Scheduler
Date: Sat, 6 May 2023 15:07:18 +0300 [thread overview]
Message-ID: <u35ftm$15ag$1@ciao.gmane.io> (raw)
In-Reply-To: <a23c9814-f4d3-88c7-fdcd-3380a1be3bae@applied-asynchrony.com>
On 03/05/2023 20:11, Holger Hoffstätte wrote:
> On 2023-05-02 21:19, Nikos Chantziaras wrote:
>> On 02/05/2023 09:53, Holger Hoffstätte wrote:
>>>> [...]
>>>> BMQ has severe issues. When emerging something while I play a game
>>>> (either native or through wine-proton,) there's long lag spikes and
>>>> freezes. Even worse, there's bugs like the system completely hanging
>>>> on shutdown, or "umount" hanging with 100% CPU use by two kernel
>>>> threads.
>>> [...]
>
> Check first if you had CONFIG_PSI enabled. The setting will work in any
> case,
> but if you already had it disabled/missing then there's no need to try
> again.
It was enabled so now I disabled it. I'm not even sure why it was
enabled in the first place, it sounds useless and is documented as "Say
N if not sure." Haven't had any issues to far.
The main thing I was hoping BMQ might be able to fix is the short sound
dropout when seeking in MPV. Meaning sound dropping out in other
applications while seeking in a video in MPV. And guess what, it indeed
fixes it. I had similar audio issues many years ago, and back then BFQ
was able to fix them.
Thanks for the help!
next prev parent reply other threads:[~2023-05-06 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 16:15 [gentoo-user] Activating BMQ CPU Scheduler Nikos Chantziaras
2023-04-26 20:06 ` [gentoo-user] " Holger Hoffstätte
2023-05-01 20:24 ` Nikos Chantziaras
2023-05-02 6:53 ` Holger Hoffstätte
2023-05-02 11:41 ` Alexe Stefan
2023-05-02 19:19 ` Nikos Chantziaras
2023-05-03 17:11 ` Holger Hoffstätte
2023-05-06 12:07 ` Nikos Chantziaras [this message]
2023-05-06 14:45 ` Holger Hoffstätte
2023-05-16 12:25 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u35ftm$15ag$1@ciao.gmane.io' \
--to=realnc@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox