From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Stephen C. Tweedie" <sct@redhat.com>,
Chaitanya Tumuluri <chait@getafix.engr.sgi.com>,
Eric Youngdale <eric@andante.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Douglas Gilbert <dgilbert@interlog.com>,
linux-scsi@vger.rutgers.edu, chait@sgi.com, linux-mm@kvack.org
Subject: Re: PATCH: Enhance queueing/scsi-midlayer to handle kiobufs. [Re: Request splits]
Date: Fri, 19 May 2000 16:55:02 +0100 [thread overview]
Message-ID: <20000519165502.G9961@redhat.com> (raw)
In-Reply-To: <20000519084842.A3373@skull.piratehaven.org>; from bapper@piratehaven.org on Fri, May 19, 2000 at 08:48:42AM -0700
Hi,
On Fri, May 19, 2000 at 08:48:42AM -0700, Brian Pomerantz wrote:
> > The real solution is probably not to increase the atomic I/O size, but
> > rather to pipeline I/Os. That is planned for the future, and now there
>
> That really depends on the device characteristics. This Ciprico
> hardware I've been working with really only performs well if the
> atomic I/O size is >= 1MB. Once you introduce additional transactions
> across the bus, your performance drops significantly. I guess it is a
> tradeoff between latency and bandwidth. Unless you mean the low level
> device would be handed a vector of kiobufs and it would build a single
> SCSI request with that vector,
ll_rw_block can already do that, but...
> then I suppose it would work well but
> the requests would have to make up a contiguous chunk of drive space.
... a single request _must_, by definition, be contiguous. There is
simply no way for the kernel to deal with non-contiguous atomic I/Os.
I'm not sure what you're talking about here --- how can an atomic I/O
be anything else? We can do scatter-gather, but only from scattered
memory, not to scattered disk blocks.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-05-19 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00c201bfc0d7$56664db0$4d0310ac@fairfax.datafocus.com>
[not found] ` <200005181955.MAA71492@getafix.engr.sgi.com>
2000-05-19 15:09 ` PATCH: Enhance queueing/scsi-midlayer to handle kiobufs. [Re: Request splits] Stephen C. Tweedie
2000-05-19 15:48 ` Brian Pomerantz
2000-05-19 15:55 ` Stephen C. Tweedie [this message]
2000-05-19 16:17 ` Brian Pomerantz
2000-05-19 18:00 ` Chaitanya Tumuluri
2000-05-19 18:11 ` Gérard Roudier
2000-05-19 19:24 ` Brian Pomerantz
2000-05-19 20:43 ` Gérard Roudier
2000-05-20 9:10 ` Change direct I/O memory model? [Was Re: PATCH: Enhance queueing/scsi-midlayer to handle kiobufs] Mark Mokryn
2000-05-19 17:53 ` PATCH: Enhance queueing/scsi-midlayer to handle kiobufs. [Re: Request splits] Chaitanya Tumuluri
2000-05-19 17:38 ` Chaitanya Tumuluri
2000-05-23 21:58 ` Chaitanya Tumuluri
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=20000519165502.G9961@redhat.com \
--to=sct@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chait@getafix.engr.sgi.com \
--cc=chait@sgi.com \
--cc=dgilbert@interlog.com \
--cc=eric@andante.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.rutgers.edu \
/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.