linux-kernel - Re: [PATCH] sched/fair: fix dlserver duplicate start and stop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Wed, 24 Apr 2024 17:59:06 -0400
From: Vineeth Remanan Pillai <vineeth@...byteword.org>
To: Daniel Bristot de Oliveira <bristot@...hat.com>
Cc: Daniel Bristot de Oliveira <bristot@...nel.org>, Ingo Molnar <mingo@...hat.com>, 
	Peter Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>, 
	Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, 
	Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, 
	Valentin Schneider <vschneid@...hat.com>, linux-kernel@...r.kernel.org, 
	Luca Abeni <luca.abeni@...tannapisa.it>, 
	Tommaso Cucinotta <tommaso.cucinotta@...tannapisa.it>, Thomas Gleixner <tglx@...utronix.de>, 
	Joel Fernandes <joel@...lfernandes.org>, Shuah Khan <skhan@...uxfoundation.org>, 
	Phil Auld <pauld@...hat.com>, Suleiman Souhlal <suleiman@...gle.com>, 
	Youssef Esmat <youssefesmat@...gle.com>
Subject: Re: [PATCH] sched/fair: fix dlserver duplicate start and stop

> > dlserver should be started on an idle root cfs rq, when
> >  - enqueue on a non-throttled cfs_rq causing the root cfs rq to
> >    go non-idle, or
> >  - untthrottle results in the root cfs rq to go non-idle.
> >
> > Similarly dlserver should be stopped on a non-idle root cfs rq, when
> >  - dequeue on a non-throttled cfs_rq causing the root cfs rq to
> >    go idle, or
> >  - throttle results in the root cfs rq to go idle.
>
>
> seem to make sense, I will add this check on v7.
>
Thanks!

> Btw, as this is an ongoing thread discussion, instead of sending a patch, next time,
> please reply to the patchset... it is easier for everybody to keep track.
>
Sorry about this. Will reply to the patchset in the future.

Thanks,
Vineeth