mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk, manfred@colorfullife.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] kill sleep_on
Date: Sat, 17 Jan 2004 22:41:39 -0800	[thread overview]
Message-ID: <20040117224139.5585fb9c.akpm@osdl.org> (raw)
In-Reply-To: <1074383111.9965.4.camel@imladris.demon.co.uk>

David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Sat, 2004-01-17 at 20:10 +0000,
> viro@parcelfarce.linux.theplanet.co.uk wrote:
> > AFAICS, _all_ uses of sleep_on() in drivers are broken in one way or another
> > and BKL won't help them.
> 
> I think ext3 and nfs get away with it at the moment by using the BKL. It
> does want fixing though.

ext3 had all its sleep_on()s and lock_kernel()s eradicated ages ago.  In
2.4 it uses sleep_on()s and lock_kernel() makes that safe.

It would be nice to fix up the lock_kernel()s in the NFS client: SMP lock
contention is quite high in there.


  reply	other threads:[~2004-01-18  6:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 18:43 Manfred Spraul
2004-01-17 19:19 ` Arjan van de Ven
2004-01-17 19:28 ` David Woodhouse
2004-01-17 20:10   ` viro
2004-01-17 23:18     ` Trond Myklebust
2004-01-17 23:45     ` David Woodhouse
2004-01-18  6:41       ` Andrew Morton [this message]
2004-01-18  6:57         ` Trond Myklebust
2004-01-18  7:05           ` Trond Myklebust
2004-01-18  7:36           ` Andrew Morton
2004-01-18  7:44             ` Manfred Spraul
2004-01-18  8:03               ` Trond Myklebust
2004-01-18  8:18                 ` Manfred Spraul
2004-01-18 17:07                   ` Trond Myklebust
2004-01-18  7:54             ` Trond Myklebust

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=20040117224139.5585fb9c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

Powered by JetHome