All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Menage <menage@google.com>,
	linux-kernel@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] Introduce down_try() so we can move away from down_trylock()
Date: Sun, 3 Aug 2008 18:33:30 +1000	[thread overview]
Message-ID: <200808031833.32048.rusty@rustcorp.com.au> (raw)
In-Reply-To: <alpine.LFD.1.10.0808011022230.3277@nehalem.linux-foundation.org>

On Saturday 02 August 2008 03:26:33 Linus Torvalds wrote:
> On Tue, 29 Jul 2008, Rusty Russell wrote:
> > Introduce down_try()
>
> I hate that name. Everybody else uses "xxx_trylock()", now you introduce a
> short version of that that just has the same return value as everybody
> else except for semaphores that admittedly were odd.

spin_lock => spin_trylock, so down => trydown.  But everyone hated that, too.

I love your suggestion tho.  Oh wait, you didn't make one...

> Also, all actual _users_ of down_trylock() seem to be prime candidates for
> turning into mutexes anyway - with the _possible_ exception of the console
> semaphore which has problems with the mutex debugging code.

And Willy is working on that.  Still.  Frankly, I gave up waiting.

> > Andrew suggested introducing "down_try" as a wrapper now, to make
> > the transition easier.
>
> The transition to WHAT? To crap?
>
> There is no need to introduce yet another temporary thing just to make
> things even _more_ confusing.

And so my patch series replaces all 21 of them.  It's a trivial replace, 
unlike sem -> mutex.

> Guys, some quality control and critical thinking, please.

Good idea.  If we'd done that we wouldn't have the down_trylock() brain 
damage.

Rusty.

  parent reply	other threads:[~2008-08-03  8:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  0:15 [PATCH] Introduce down_try() so we can move away from down_trylock() Rusty Russell
2008-07-29  0:27 ` Paul Menage
2008-07-29 13:01   ` Rusty Russell
2008-07-29 16:21     ` Randy Dunlap
2008-07-29 23:56       ` Rusty Russell
2008-08-01 17:26     ` Linus Torvalds
2008-08-01 17:40       ` Andrew Morton
2008-08-01 18:22         ` Linus Torvalds
2008-08-03  8:33       ` Rusty Russell [this message]
2008-08-03 13:07         ` Matthew Wilcox
2008-08-03 17:33         ` Linus Torvalds
2008-08-03 17:35           ` Linus Torvalds
2008-08-04  3:28             ` Rusty Russell
2008-08-04  5:53               ` Linus Torvalds
2008-08-04  7:57                 ` Rusty Russell
2008-08-04  8:45                   ` Alan Cox
2008-08-04 11:43                     ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808031833.32048.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=menage@google.com \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.