[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFy=CnCLet=B9Q5dYU9w885sXNuYVDSkjHAp5V+nczbn3Q@mail.gmail.com>
Date: Thu, 3 Jul 2014 08:35:49 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jason Low <jason.low2@...com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>,
Waiman Long <Waiman.Long@...com>,
Davidlohr Bueso <davidlohr@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Anvin <hpa@...or.com>, Andi Kleen <andi@...stfloor.org>,
Jej B <James.Bottomley@...senpartnership.com>,
Steven Rostedt <rostedt@...dmis.org>,
Tim Chen <tim.c.chen@...ux.intel.com>,
"Chandramouleeswaran, Aswin" <aswin@...com>,
"Norton, Scott J" <scott.norton@...com>,
"Vinod, Chegu" <chegu_vinod@...com>
Subject: Re: [RFC] Cancellable MCS spinlock rework
On Thu, Jul 3, 2014 at 8:31 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I don't think we'll support 2 _billion_ processes/threads waiting on
> the same semaphore any time soon, so the 'long' seems a bit of an
> overkill on 64-bit architectures.
Oh, never mind. The 'struct semaphore' uses it as just a plain count,
but the rwsem ends up splitting up the bits for readers/writers, so we
actually do want the full 64-bit value there.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists