xfs
[Top] [All Lists]

Re: [PATCH 1/1] Replace down_trylock() with down_try(), reverse return v

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH 1/1] Replace down_trylock() with down_try(), reverse return values.
From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Date: Mon, 5 May 2008 16:09:12 +1000
Cc: linux-kernel@xxxxxxxxxxxxxxx, gregkh@xxxxxxx, kaos@xxxxxxx, Stephen Rothwell <sfr@xxxxxxxxxxx>, rolandd@xxxxxxxxx, "Brian S. Julin" <bri@xxxxxxxxx>, Martin Diehl <info@xxxxxxxxx>, mokuno@xxxxxxxxxxxxx, aacraid@xxxxxxxxxxx, mfasheh@xxxxxxxx, wim@xxxxxxxxx, xfs@xxxxxxxxxxx, reiserfs-devel@xxxxxxxxxxxxxxx, Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
In-reply-to: <20080505055823.GA20970@xxxxxxxxxxxxx>
References: <200805051156.36437.rusty@xxxxxxxxxxxxxxx> <20080505055823.GA20970@xxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.9.9
On Monday 05 May 2008 15:58:23 Christoph Hellwig wrote:
> On Mon, May 05, 2008 at 01:56:35AM +0000, Rusty Russell wrote:
> > down_trylock() returns 1 on failure, 0 on success.  This differs from
> > spin_trylock(), mutex_trylock() and common sense.  Or as ocfs2 put it
> > "kernel 1, world 0".
> >
> > Rename it to down_try() (which makes more sense anyway), and reverse
> > it.  Fortunately there aren't a huge number of callers left.
>
> Given that people are actively trying to kill struct semaphore I don't
> think doing a big search and rename is a good idea right now.

If it goes away before the 2.6.27 merge window, great.  But I don't see that 
happening, so let's clean up this horror.  I cc'd all the people effected in 
the hope that it will prod some of them towards mutexes anyway.

> (And I also really hate the name down_try, but when it goes away that's
>  rather void and we can spare the discussion)

Ideas?  down() is pretty bad, down_try() matches it.

Thanks,
Rusty.


<Prev in Thread] Current Thread [Next in Thread>