[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080415174109.GD9191@parisc-linux.org>
Date: Tue, 15 Apr 2008 11:41:09 -0600
From: Matthew Wilcox <matthew@....cx>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andi Kleen <andi@...stfloor.org>,
Peter Zijlstra <peterz@...radead.org>,
Bart Van Assche <bart.vanassche@...il.com>,
Roland Dreier <rdreier@...co.com>, Ingo Molnar <mingo@...e.hu>,
Ingo Oeser <ioe-lkml@...eria.de>,
Daniel Walker <dwalker@...sta.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Replace completions with semaphores
On Tue, Apr 15, 2008 at 10:26:21AM -0700, Linus Torvalds wrote:
> MUCH more trivial than this complex series.
>
> (You may think that the "Replace completions with semaphores" patch is not
> very complicated, but it *is* - it depends very intimately on the big
> patch-series that basically turns semaphores into what completions are
> now!)
complex? big? The big bits are dealing with renaming asm/semaphore.h to
linux/semaphore.h, and I've dropped those out now. There's a couple of
up-front patches which add inclusions of asm/semaphore.h to files which
were missing it. Then I add the new semaphore implementation, delete
the old ones, and add the down_timeout() and down_killable() functions.
> In other words, what makes me not like this is hat we first turn
> semaphores into the generic code (which is largely what completions were:
> just a special case of the generic semaphores!) and then turns completions
> into these things. That just doesn't make any sense to me!
Blame me for not realising that completions were semaphores under a
different name.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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