[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080521080452.GA1305@infradead.org>
Date: Wed, 21 May 2008 04:04:53 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <matthew@....cx>
Subject: Re: [PATCH] Introduce down_nowait()
On Tue, May 20, 2008 at 11:29:03PM -0700, Andrew Morton wrote:
> Actually, I don't thing down_nowait() is a terribly good name, because it
> doesn't tell the reader anything about what to expect from the return
> value. Does a non-zero return mean that down_wait() acquired the lock,
> or does it not? Something like down_try() would be better, because if
> it returns 1 we can say "ah, the trying succeeded".
Actually, it does, and the kerneldoc comment explains it in every detail
for those who need to read it up. Then again semaphores and on their
way out, and I really hate the kind of churn this thing introduces at
this moment. Please let all the semaphore to completion/mutex/other
construct change settle for a while, and with a little chance this gem
will just go away entirely.
--
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