[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    [gentoo-user] Re: Activating BMQ CPU Scheduler
From:       Holger_Hoffstätte <holger () applied-asynchrony ! com>
Date:       2023-05-06 14:45:54
Message-ID: 9b4b8c1f-f14d-df3f-b949-41485e4e5904 () applied-asynchrony ! com
[Download RAW message or body]

On 2023-05-06 14:07, Nikos Chantziaras wrote:
> 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.

Great! PSI is extremely useful, but was made primarily for servers,
though there are potentially interesting use cases for dektop systems
as well. It does come at a slight cost at runtime though, so unless you're
using it it's probably better to just disable it.

See https://www.kernel.org/doc/html/latest/accounting/psi.html and
https://facebookmicrosites.github.io/psi/docs/overview for more.

Unfortunately it seems that a recent change in the mainline kernel
introduced a bit of an incompatibility, which is why the BMQ/PDS patch
now turns it off. We're trying to get that incompatibility fixed.

Anyway: glad you're up and running now!

cheers
Holger

[prev in list] [next in list] [prev in thread] [next in thread]