public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Announce: Semaphore-Removal tree
Date: Fri, 25 Apr 2008 13:24:09 -0700	[thread overview]
Message-ID: <1209155049.12461.40.camel@localhost.localdomain> (raw)
In-Reply-To: <20080425170021.GH14990@parisc-linux.org>


On Fri, 2008-04-25 at 11:00 -0600, Matthew Wilcox wrote:
> It's been a Good Idea for a while to use mutexes instead of
> semaphores where possible.  Additional debuggability, better optimised,
> better-enforced semantics, etc.
> 
> Obviously, there are some places that can't be converted to mutexes.
> I'm not proposing blind changes.  I've been through a dozen places
> and found some that can be converted to spinlocks, others to
> completions, but mostly to mutexes.  So as not to lose these patches,
> I've made them available as a git tree.  I think the right way to get
> these patches in will be to go through the maintainers of each file.
> 
> I'll post a list of the places using semaphores later.  My current list
> is a bit out of date and contains insulting comments that I would like
> to rephrase before the authors of the code in question see them ;-)

I've got a bunch of these if you want to incorporate them.. I've been
slowly trickling them up stream ..

Daniel


  reply	other threads:[~2008-04-25 20:24 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 [this message]
2008-04-25 20:38 ` Daniel Walker
2008-04-25 21:12   ` Christoph Hellwig
2008-04-25 21:22     ` Daniel Walker
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=1209155049.12461.40.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox