[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1908010240260.1788@nanos.tec.linutronix.de>
Date: Thu, 1 Aug 2019 02:41:20 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Gabriel Krisman Bertazi <krisman@...labora.com>
cc: mingo@...hat.com, peterz@...radead.org, dvhart@...radead.org,
linux-kernel@...r.kernel.org, kernel@...labora.com
Subject: Re: [PATCH RFC 1/2] futex: Split key setup from key queue locking
and read
On Wed, 31 Jul 2019, Gabriel Krisman Bertazi wrote:
> Thomas Gleixner <tglx@...utronix.de> writes:
>
> > On Tue, 30 Jul 2019, Gabriel Krisman Bertazi wrote:
> >
> >> split the futex key setup from the queue locking and key reading. This
> >> is useful to support the setup of multiple keys at the same time, like
> >> what is done in futex_requeue() and what will be done for the
> >
> > What has this to do with futex_requeue()? Absolutely nothing unleass you
> > can reused that code there, which I doubt.
>
> futex_requeue is another place where more than one key is setup at a
> time. Just that. I think it could be reused there, but this change is
> out of scope for this patch.
No it can't. And if it could, then it would be definitely in scope of this
patch set to reuse functionality.
Thanks,
tglx
Powered by blists - more mailing lists