From: A Duston <hald@sound.net>
To: Jens Axboe <axboe@suse.de>
Cc: "Gortmaker, Paul" <p_gortmaker@yahoo.com>,
"Andersen, Rasmus" <rasmus@jaquet.dk>,
linux-kernel@vger.kernel.org
Subject: Re: PS/2 Esdi patch #8
Date: Sat, 26 May 2001 10:33:49 -0500 [thread overview]
Message-ID: <3B0FCCDD.5B5A891C@sound.net> (raw)
In-Reply-To: <Pine.GSO.4.10.10105231748550.23376-200000@sound.net> <3B0D733F.1829DC88@yahoo.com> <20010525164615.C14899@suse.de> <3B0FC26B.D210E416@sound.net> <20010526165800.C553@suse.de>
Jens Axboe wrote:
>
> --snip--
>
> and so it continues. This is the easy way to process requests. However,
> if you can start I/O on more than one buffer at the time (scatter
> gather), you could then setup your sg tables by browsing the entire
> request buffer_head list and initiate I/O as needed.
>
> Bigger requests on the queue, means more I/O in progress being possible.
> There's no rule that you have to finish a request in one go, so even if
> you can only handle eg 64 sectors per request with sg, you could do
> just start I/O on as many segments as you can and simply don't dequeue
> the request until it's completely done. So the max_sectors patch is
> never really needed if you know what you are doing.
Can I still gain any advantage if the hardware can only have one I/O inflight
per device? I am not sure the ps2esdi interface supports this.
Hal Duston
hald@sound.net
next prev parent reply other threads:[~2001-05-26 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 22:54 PS/2 Esdi patch #8 Hal Duston
2001-05-24 20:46 ` Paul Gortmaker
2001-05-25 14:46 ` Jens Axboe
2001-05-26 9:53 ` Paul Gortmaker
2001-05-26 14:49 ` A Duston
2001-05-26 14:58 ` Jens Axboe
2001-05-26 15:33 ` A Duston [this message]
2001-05-26 15:40 ` Jens Axboe
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=3B0FCCDD.5B5A891C@sound.net \
--to=hald@sound.net \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=rasmus@jaquet.dk \
/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.