From: Andi Kleen <andi@firstfloor.org>
To: David Chinner <dgc@sgi.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org, knikanth@novell.com
Subject: Re: [PATCH 0/6] IO context sharing
Date: 23 Jan 2008 09:44:54 +0100 [thread overview]
Message-ID: <p73sl0plym1.fsf@crumb.suse.de> (raw)
In-Reply-To: <20080123035001.GL155259@sgi.com>
David Chinner <dgc@sgi.com> writes:
> On Tue, Jan 22, 2008 at 10:49:15AM +0100, Jens Axboe wrote:
> > Hi,
> >
> > Today io contexts are per-process and define the (surprise) io context
> > of that process. In some situations it would be handy if several
> > processes share an IO context.
>
> I think that the nfsd threads should probably share as
> well. It should probably provide an io context per thread
> pool....
Wouldn't it make more sense to have an own io context for each
NFS client in this case? Ok that does mean some state per remote
client, but nfsd already keeps that anyways so it would be probably
not too much work to tug an io context in there too.
-Andi
prev parent reply other threads:[~2008-01-23 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 9:49 [PATCH 0/6] IO context sharing Jens Axboe
2008-01-22 9:49 ` [PATCH 1/6] ioprio: move io priority from task_struct to io_context Jens Axboe
2008-01-23 22:07 ` Andrew Morton
2008-01-24 7:30 ` Jens Axboe
2008-01-22 9:49 ` [PATCH 2/6] io context sharing: preliminary support Jens Axboe
2008-01-23 22:08 ` Andrew Morton
2008-01-24 7:36 ` Jens Axboe
2008-01-22 9:49 ` [PATCH 3/6] io_context sharing - cfq changes Jens Axboe
2008-01-22 9:49 ` [PATCH 4/6] block: cfq: make the io contect sharing lockless Jens Axboe
2008-01-23 22:08 ` Andrew Morton
2008-01-24 7:36 ` Jens Axboe
2008-01-24 16:42 ` Paul E. McKenney
2008-01-22 9:49 ` [PATCH 5/6] io_context sharing - anticipatory changes Jens Axboe
2008-01-22 9:49 ` [PATCH 6/6] kernel: add CLONE_IO to specifically request sharing of IO contexts Jens Axboe
2008-01-22 14:49 ` [PATCH 0/6] IO context sharing Peter Zijlstra
2008-01-22 18:21 ` Jens Axboe
2008-01-23 3:50 ` David Chinner
2008-01-23 8:44 ` Andi Kleen [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=p73sl0plym1.fsf@crumb.suse.de \
--to=andi@firstfloor.org \
--cc=dgc@sgi.com \
--cc=jens.axboe@oracle.com \
--cc=knikanth@novell.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).