[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7703f6ae-51b9-8bc4-a3c0-70f534451014@oracle.com>
Date: Wed, 21 Apr 2021 10:45:18 -0400
From: Chris Hyser <chris.hyser@...cle.com>
To: Peter Zijlstra <peterz@...radead.org>,
Joel Fernandes <joel@...lfernandes.org>
Cc: Tejun Heo <tj@...nel.org>, Hao Luo <haoluo@...gle.com>,
Josh Don <joshdon@...gle.com>, Ingo Molnar <mingo@...nel.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Valentin Schneider <valentin.schneider@....com>,
Mel Gorman <mgorman@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Glexiner <tglx@...utronix.de>,
Michal Koutný <mkoutny@...e.com>,
Christian Brauner <christian.brauner@...ntu.com>,
Zefan Li <lizefan.x@...edance.com>
Subject: Re: [PATCH 0/9] sched: Core scheduling interfaces
On 4/21/21 9:35 AM, Peter Zijlstra wrote:
> On Mon, Apr 19, 2021 at 11:00:57AM +0200, Peter Zijlstra wrote:
>> On Sat, Apr 17, 2021 at 09:35:07PM -0400, Joel Fernandes wrote:
>
>>> Peter, any thoughts on this?
>>
>> Adding CGROUP_SHARE is not sufficient to close the hole against CLEAR.
>> So we either then have to 'tweak' the meaning of CLEAR or replace it
>> entirely, neither seem attractive.
>>
>>
>> I'd love to make some progress on all this.
>
> Can I comment out CLEAR so we can sort that out later? I suppose people
I merely added CLEAR for completeness. Ultimately, I think having to kill a process because a cookie got set by mistake
is bad, but it can absolutely be sorted out later.
-chrish
Powered by blists - more mailing lists