From: Jens Axboe <jens.axboe@oracle.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
Nick Piggin <npiggin@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@suse.de>, Mark Fasheh <mark.fasheh@oracle.com>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>
Subject: Re: [PATCH] 4/4 block: explicit plugging
Date: Fri, 5 Jan 2007 08:23:05 +0100 [thread overview]
Message-ID: <20070105072305.GN11203@kernel.dk> (raw)
In-Reply-To: <459C8427.9040704@yahoo.com.au>
On Thu, Jan 04 2007, Nick Piggin wrote:
> Jens Axboe wrote:
> >Nick writes:
> >
> >This is a patch to perform block device plugging explicitly in the
> >submitting
> >process context rather than implicitly by the block device.
>
> Hi Jens,
>
> Hey thanks for doing so much hard work with this, I couldn't have fixed
> all the block layer stuff myself. QRCU looks like a good solution for the
> barrier/sync operations (/me worried that one wouldn't exist), and a
> novel use of RCU!
>
> The only thing I had been thinking about before it is ready for primetime
> -- as far as the VM side of things goes -- is whether we should change
> the hard calls to address_space operations, such that they might be
> avoided or customised when there is no backing block device?
>
> I'm sure the answer to this is "yes", so I have an idea for a simple
> implementation... but I'd like to hear thoughts from network fs / raid
> people?
I suppose that would be the proper thing to do, for non __make_request()
operated backing devices. I'll add the hooks, then we can cook up a raid
implementation if need be.
--
Jens Axboe
prev parent reply other threads:[~2007-01-05 7:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 7:48 [BLOCK] 0/4 explicit io plugging Jens Axboe
2007-01-03 7:48 ` [PATCH] 1/4 qrcu: "quick" srcu implementation Jens Axboe
2007-01-03 7:48 ` [PATCH] 2/4 qrcu: add rcutorture test Jens Axboe
2007-01-03 8:31 ` [PATCH] 3/4 qrcu: add documentation Jens Axboe
2007-01-03 9:29 ` Tomas Carnecky
2007-01-03 9:39 ` Jens Axboe
2007-01-03 9:41 ` [PATCH] 4/4 block: explicit plugging Jens Axboe
[not found] ` <1167810508576-git-send-email-jens.axboe@oracle.com>
2007-01-03 8:09 ` Andrew Morton
2007-01-03 8:22 ` Jens Axboe
2007-01-03 21:50 ` Chen, Kenneth W
2007-01-03 22:29 ` Jens Axboe
2007-01-03 22:34 ` Chen, Kenneth W
2007-01-04 14:39 ` Jens Axboe
2007-01-05 22:04 ` Chen, Kenneth W
2007-01-04 4:35 ` Nick Piggin
2007-01-05 7:23 ` Jens Axboe [this message]
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=20070105072305.GN11203@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=neilb@suse.de \
--cc=nickpiggin@yahoo.com.au \
--cc=npiggin@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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.