[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e63ca3f4-283a-05fb-d637-c7428d87c8f2@efficios.com>
Date: Fri, 26 May 2023 14:58:53 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Waiman Long <longman@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
torvalds@...ux-foundation.org, keescook@...omium.org,
gregkh@...uxfoundation.org, pbonzini@...hat.com
Cc: linux-kernel@...r.kernel.org, ojeda@...nel.org,
ndesaulniers@...gle.com, mingo@...hat.com, will@...nel.org,
boqun.feng@...il.com, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com, paulmck@...nel.org,
frederic@...nel.org, quic_neeraju@...cinc.com,
joel@...lfernandes.org, josh@...htriplett.org,
jiangshanlai@...il.com, qiang1.zhang@...el.com,
rcu@...r.kernel.org, tj@...nel.org, tglx@...utronix.de
Subject: Re: [RFC][PATCH 1/2] locking: Introduce __cleanup__ based guards
On 5/26/23 14:49, Waiman Long wrote:
[...]
>
> BTW, do we have a use case for double_lock_guard/double_lock_scope? I
> can envision a nested lock_scope inside a lock_scope, but taking 2 auto
> locks of the same type at init time and then unlock them at exit just
> doesn't make sense to me.
AFAIU taking both runqueue locks for source and destination runqueues on
migration is one use-case for double_lock_guard/scope.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
Powered by blists - more mailing lists