From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Miquel van Smoorenburg <miquels@cistron.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backing dev unplugging
Date: Thu, 11 Mar 2004 07:43:45 +0100 [thread overview]
Message-ID: <20040311064345.GB6955@suse.de> (raw)
In-Reply-To: <20040310150542.13d71a39.akpm@osdl.org>
On Wed, Mar 10 2004, Andrew Morton wrote:
>
> (Please use reply-to-all)
>
> "Miquel van Smoorenburg" <miquels@cistron.nl> wrote:
> >
> > In article <20040310210207.GL15087@suse.de>,
> > Jens Axboe <axboe@suse.de> wrote:
> > >On Wed, Mar 10 2004, Andrew Morton wrote:
> > >> Jens Axboe <axboe@suse.de> wrote:
> > >> >
> > >> > Here's a first cut at killing global plugging of block devices to reduce
> > >> > the nasty contention blk_plug_lock caused.
> > >>
> > >> Shouldn't we take read_lock(&md->map_lock) in dm_table_unplug_all()?
> > >
> > >Ugh yes, we certainly should.
> >
> > With the latest patches from Joe it would be more like
> >
> > map = dm_get_table(md);
> > if (map) {
> > dm_table_unplug_all(map);
> > dm_table_put(map);
> > }
> >
> > No lock ranking issues, you just get a refcounted map (table, really).
>
> Ah, OK. Jens, you'll be needing this (on rc2-mm1):
>
> dm.c: protect md->map with a rw spin lock rather than the md->lock
> semaphore. Also ensure that everyone accesses md->map through
> dm_get_table(), rather than directly.
Neato, much better. I'll build on top of that.
--
Jens Axboe
next prev parent reply other threads:[~2004-03-11 6:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 12:45 [PATCH] backing dev unplugging Jens Axboe
2004-03-10 19:55 ` Andrew Morton
2004-03-10 20:03 ` Kenneth Chen
2004-03-10 20:20 ` Jens Axboe
2004-03-10 20:45 ` Jesse Barnes
2004-03-10 20:49 ` Jens Axboe
[not found] ` <20040310205237.GK15087@suse.de>
2004-03-10 21:01 ` Jesse Barnes
2004-03-10 21:02 ` Jens Axboe
2004-03-10 21:35 ` Jesse Barnes
2004-03-10 23:54 ` Andrew Morton
2004-03-11 0:03 ` David Mosberger
2004-03-11 6:30 ` Jesse Barnes
2004-03-10 20:17 ` Jens Axboe
2004-03-15 5:53 ` Kenneth Chen
2004-03-10 20:14 ` Jeff Garzik
2004-03-10 20:19 ` Jens Axboe
2004-03-10 21:00 ` Andrew Morton
2004-03-10 21:02 ` Jens Axboe
2004-03-10 21:40 ` Miquel van Smoorenburg
2004-03-10 23:05 ` Andrew Morton
2004-03-11 0:05 ` Miquel van Smoorenburg
2004-03-11 0:17 ` Andrew Morton
2004-03-11 6:43 ` Jens Axboe [this message]
2004-03-10 22:22 ` Nathan Scott
2004-03-10 23:32 ` Steve Lord
2004-03-11 7:05 ` Jens Axboe
2004-03-11 9:14 ` Joe Thornber
2004-03-11 9:16 ` Jens Axboe
2004-03-11 12:17 ` Christophe Saout
2004-03-11 12:22 ` Jens Axboe
2004-03-11 13:11 ` Christophe Saout
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=20040311064345.GB6955@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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