linux-kernel - Re: [PATCH v11 7/7] sched: Split scheduler and execution contexts

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240731103238.5e45e343@gandalf.local.home>
Date: Wed, 31 Jul 2024 10:32:38 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Juri Lelli <juri.lelli@...hat.com>, John Stultz <jstultz@...gle.com>,
 LKML <linux-kernel@...r.kernel.org>, Joel Fernandes <joelaf@...gle.com>,
 Qais Yousef <qyousef@...alina.io>, Ingo Molnar <mingo@...hat.com>, Vincent
 Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann
 <dietmar.eggemann@....com>, Valentin Schneider <vschneid@...hat.com>, Ben
 Segall <bsegall@...gle.com>, Zimuzo Ezeozue <zezeozue@...gle.com>, Youssef
 Esmat <youssefesmat@...gle.com>, Mel Gorman <mgorman@...e.de>, Will Deacon
 <will@...nel.org>, Waiman Long <longman@...hat.com>, Boqun Feng
 <boqun.feng@...il.com>, "Paul E. McKenney" <paulmck@...nel.org>, Xuewen Yan
 <xuewen.yan94@...il.com>, K Prateek Nayak <kprateek.nayak@....com>, Metin
 Kaya <Metin.Kaya@....com>, Thomas Gleixner <tglx@...utronix.de>, Daniel
 Lezcano <daniel.lezcano@...aro.org>, kernel-team@...roid.com, Connor
 O'Brien <connoro@...gle.com>
Subject: Re: [PATCH v11 7/7] sched: Split scheduler and execution contexts

On Wed, 31 Jul 2024 13:37:20 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> > I don't think I have strong preferences either way, but I actually
> > considered the proxy to be the blocked donor (the one picked by the
> > scheduler to run), as it makes the owner use its properties, acting as a
> > proxy for the owner.  
> 
> This. But I suspect we both suffer from not being native English
> speakers.

Has nothing to do with being a native English speaker or not. "proxy" is
not a commonly used word and can easily be misused.

> 
> Would 'donor' work in this case?
> 
> Then the donor gets all the accounting done on it, while we execute
> curr.

I agree that "donor" is a bit easier to understand.

-- Steve