[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131105091351.30d1e913@gandalf.local.home>
Date: Tue, 5 Nov 2013 09:13:51 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
paulmck@...ux.vnet.ibm.com, oleg@...hat.com, dhowells@...hat.com,
willy@...ux.intel.com, tglx@...utronix.de, airlied@...il.com,
maarten.lankhorst@...onical.com, walken@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/8] Move locking primitives into kernel/locking/
On Tue, 5 Nov 2013 14:26:09 +0100
Ingo Molnar <mingo@...nel.org> wrote:
>
> * Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Also, 'kernel lock' brings me back memories of the 'big kernel lock' -
> while 'kernel locks' brings verb/noun ambiguity and visuals of
> 'kernel locks up'.
Of course "locking" is only a verb, and we get "kernel locking up"
too ;-)
>
> As for typing legth: kernel/lo<Tab> autocompletion is your friend! :-)
>
> All in one, I think kernel/locking/ is a better name.
Fine, but I just love the idea of having the choice between a bagel and
cream cheese or with kernel lox.
-- Steve
--
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