From: "Dan Williams" <dan.j.williams@intel.com>
To: "device-mapper development" <dm-devel@redhat.com>
Cc: "Hirokazu Takahashi" <taka@valinux.co.jp>,
linux-kernel@vger.kernel.org, agk@sourceware.org
Subject: Re: [dm-devel] Re: [RFC][PATCH 0/10] I/O context inheritance
Date: Tue, 22 Apr 2008 11:10:41 -0700 [thread overview]
Message-ID: <e9c3a7c20804221110y1968dfb3q27b86c9a7480ad1@mail.gmail.com> (raw)
In-Reply-To: <20080422145418.GL12774@kernel.dk>
On Tue, Apr 22, 2008 at 7:54 AM, Jens Axboe <jens.axboe@oracle.com> wrote:
> On Tue, Apr 22 2008, Hirokazu Takahashi wrote:
> > Hi,
> >
> > Sorry, these patches are for linux-2.6.25.
> >
> > > This series of patches make the block I/O layer and the I/O schedulers
> > > be able to determine the right io_context of every I/O.
> > >
> > > The current implementation of the block I/O layer and the I/O schedulers
> > > assume that the current process is the one which issued the given I/O,
> > > then use the io_context of this process to control the I/O.
> > > But this assumption isn't quite right because several kernel threads
> > > will handle I/O requests on behalf of the processes which originated them.
> > > This often happens when you want to use device mapper modules.
> > >
> > > The patches make every bio has a pointer to an io_context, which will
> > > be set when it is allocated or cloned. So it makes it possible to find
> > > the right io_context from any bio at any place.
> > >
> > > I'm waiting for your comments.
>
> Can you give a brief summary of what you need this stuff for?
>
I am not sure if this the intended application, but I have been
looking at supporting ionice over software-raid and this series seems
like a necessary first step.
--
Dan
next prev parent reply other threads:[~2008-04-22 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 13:49 taka
2008-04-22 13:51 ` [RFC][PATCH 1/10] I/O context inheritance Hirokazu Takahashi
2008-04-22 13:53 ` [RFC][PATCH 2/10] " Hirokazu Takahashi
2008-04-22 13:53 ` [RFC][PATCH 3/10] " Hirokazu Takahashi
2008-04-22 13:54 ` [RFC][PATCH 4/10] " Hirokazu Takahashi
2008-04-22 13:55 ` [RFC][PATCH 5/10] " Hirokazu Takahashi
2008-04-22 13:55 ` [RFC][PATCH 6/10] " Hirokazu Takahashi
2008-04-22 13:57 ` [RFC][PATCH 7/10] " Hirokazu Takahashi
2008-04-22 13:58 ` [RFC][PATCH 8/10] " Hirokazu Takahashi
2008-04-22 13:59 ` [RFC][PATCH 9/10] " Hirokazu Takahashi
2008-04-22 14:00 ` [RFC][PATCH 10/10] " Hirokazu Takahashi
2008-04-22 14:03 ` [RFC][PATCH 0/10] " Hirokazu Takahashi
2008-04-22 14:54 ` Jens Axboe
2008-04-22 18:10 ` Dan Williams [this message]
2008-04-23 3:27 ` [dm-devel] " Hirokazu Takahashi
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=e9c3a7c20804221110y1968dfb3q27b86c9a7480ad1@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=agk@sourceware.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
/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
all inboxes | Powered by JetHome®