From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net
Subject: Re: Fw: Writeup on AIO design (uploaded) - corrected url
Date: Wed, 30 Jan 2002 21:30:47 +0530 [thread overview]
Message-ID: <20020130213047.A2143@in.ibm.com> (raw)
In-Reply-To: <20020130205115.B1864@in.ibm.com> <20020130104627.N10157@devserv.devel.redhat.com>
In-Reply-To: <20020130104627.N10157@devserv.devel.redhat.com>; from jakub@redhat.com on Wed, Jan 30, 2002 at 10:46:27AM -0500
On Wed, Jan 30, 2002 at 10:46:27AM -0500, Jakub Jelinek wrote:
> On Wed, Jan 30, 2002 at 08:51:15PM +0530, Suparna Bhattacharya wrote:
> >
> > Oops, oops, oops, I mispelt the website.
> > It should have been:
> >
> > http://lse.sourceforge.net/io/aionotes.txt
>
> a. User level threads
> - glibc approach (one user thread per operation ?)
> poor scalability, performance
>
> Glibc uses a pool of threads, not one thread per operation.
> All requests against a single file descriptor are served sequentially,
> while for different fds they are served by different threads unless aio
> thread limit has been reached, in which case they are queued too.
Thanks for the clarification.
What is the aio thread limit like ?
>
> b. Pool of threads
> - have a pool of threads servicing an aio request queue for the
> task - tradeof between degree of concurrency/utilization and
> resource consumption.
>
> Jakub
next prev parent reply other threads:[~2002-01-30 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 15:21 Fw: Writeup on AIO design (uploaded) - corrected url Suparna Bhattacharya
2002-01-30 15:46 ` Jakub Jelinek
2002-01-30 16:00 ` Suparna Bhattacharya [this message]
2002-01-30 16:03 ` Jakub Jelinek
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=20020130213047.A2143@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=jakub@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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