[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1605071044540.3540@nanos>
Date: Sat, 7 May 2016 10:45:57 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Darren Hart <dvhart@...radead.org>
cc: LKML <linux-kernel@...r.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Darren Hart <darren@...art.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Michael Kerrisk <mtk.manpages@...glemail.com>,
Davidlohr Bueso <dave@...olabs.net>, Chris Mason <clm@...com>,
Carlos O'Donell <carlos@...hat.com>,
Torvald Riegel <triegel@...hat.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [patch V2 2/7] futex: Hash private futexes per process
On Fri, 6 May 2016, Darren Hart wrote:
> It would be good to have a way to detect that the process private hash table was
> > successfully created. Perhaps a /proc/pid/ feature? This would allow us to write
> > a functional futex test for tools/testing/selftests/futex
>
> I suppose we could just use FUTEX_PREALLOC_HASH for this purpose, passing in the
> default hash size. This will either return the default, the previously set
> value, or 0, indicating the global hash is being used. That should be sufficient
> for programatically determining the state of the system.
Right.
> The /proc/pid/futex_hash_size option may still be convenient for other purposes.
> Perhaps with a -1 indicating it hasn't been set yet.
Dunno, whether that's valuable, but it can be done on top.
Thanks,
tglx
Powered by blists - more mailing lists