From: Daniel Walker <dwalker@mvista.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Announce: Semaphore-Removal tree
Date: Fri, 25 Apr 2008 14:22:31 -0700 [thread overview]
Message-ID: <1209158552.12461.53.camel@localhost.localdomain> (raw)
In-Reply-To: <20080425211250.GA13858@infradead.org>
On Fri, 2008-04-25 at 17:12 -0400, Christoph Hellwig wrote:
> On Fri, Apr 25, 2008 at 01:38:37PM -0700, Daniel Walker wrote:
> > I was reviewing your patches, and I don't like the semaphore to spinlock
> > changes.. There's no reason to start adding spinlocks, unless it's
> > really performance sensitive which none of those places are..
>
> Yes, there is. The spinlock is our most efficient locking primitive
> for the normal mostly un-contentded case. Please get out of your
> realtime-ghetto.
If you can make a case for converting some semaphores to spinlocks be my
guest .. If you have good reasoning I wouldn't stand in the way.. (Real
time converts all the spinlocks to mutexes anyway ..)
Daniel
next prev parent reply other threads:[~2008-04-25 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 17:00 Announce: Semaphore-Removal tree Matthew Wilcox
2008-04-25 20:24 ` Daniel Walker
2008-04-25 20:38 ` Daniel Walker
2008-04-25 21:12 ` Christoph Hellwig
2008-04-25 21:22 ` Daniel Walker [this message]
2008-04-26 9:30 ` Christoph Hellwig
2008-04-26 13:39 ` Peter Zijlstra
2008-04-26 13:44 ` Christoph Hellwig
2008-04-26 14:04 ` Peter Zijlstra
2008-04-28 4:59 ` David Chinner
2008-04-26 13:54 ` Stephen Rothwell
2008-04-26 15:59 ` Matthew Wilcox
2008-04-26 16:43 ` Stephen Rothwell
2008-04-28 5:10 ` David Chinner
2008-04-28 12:20 ` Matthew Wilcox
2008-04-29 0:09 ` David Chinner
2008-04-29 2:35 ` Matthew Wilcox
2008-04-29 3:56 ` David Chinner
2008-04-30 10:21 ` Matthew Wilcox
2008-04-30 10:06 ` Matthew Wilcox
2008-04-30 11:01 ` David Chinner
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=1209158552.12461.53.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sfr@canb.auug.org.au \
/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.