From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: mingo@elte.hu
Cc: Benjamin LaHaise <bcrl@redhat.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-aio@kvack.org, kiobuf-io-devel@lists.sourceforge.net,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [Kiobuf-io-devel] Re: 1st glance at kiobuf overhead in kernelaiovs pread vs user aio
Date: Fri, 02 Feb 2001 16:37:44 -0800 [thread overview]
Message-ID: <3A7B52D8.733CFECC@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102030023530.8627-100000@elte.hu>
Ingo Molnar wrote:
>
> On Fri, 2 Feb 2001, Rajagopal Ananthanarayanan wrote:
>
> > Do you really have worker threads? In my reading of the patch it seems
> > that the wtd is serviced by keventd. [...]
>
> i think worker threads (or any 'helper' threads) should be avoided. It can
> be done without any extra process context, and it should be done that way.
> Why all the trouble with async IO requests if requests are going to end up
> in a worker thread's context anyway? (which will be a serializing point,
> otherwise why does it end up there?)
>
Good point. Can you expand on how you plan to service pending
chunks of work (eg. issuing readpage() on some pages) without
the use of threads?
thanks,
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-03 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 19:32 1st glance at kiobuf overhead in kernel aio vs pread vs user aio bcrl
2001-02-02 20:18 ` Ingo Molnar
2001-02-02 20:45 ` [Kiobuf-io-devel] " Benjamin LaHaise
2001-02-02 23:14 ` Ingo Molnar
2001-02-02 23:19 ` [Kiobuf-io-devel] Re: 1st glance at kiobuf overhead in kernelaio " Rajagopal Ananthanarayanan
2001-02-02 23:30 ` Ingo Molnar
2001-02-03 0:37 ` Rajagopal Ananthanarayanan [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=3A7B52D8.733CFECC@sgi.com \
--to=ananth@sgi.com \
--cc=bcrl@redhat.com \
--cc=kiobuf-io-devel@lists.sourceforge.net \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
/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.