From: Jens Axboe <axboe@suse.de>
To: Valdis.Kletnieks@vt.edu, Nick Piggin <piggin@cyberone.com.au>
Cc: Giuliano Pochini <pochini@shiny.it>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kernel@alex.org.uk, Alex Tomas <bzzz@tmi.comex.ru>,
Andrew Morton <akpm@digeo.com>,
Oliver Xymoron <oxymoron@waste.org>
Subject: Re: 2.5.59-mm5
Date: Fri, 24 Jan 2003 21:04:34 +0100 [thread overview]
Message-ID: <20030124200434.GD889@suse.de> (raw)
In-Reply-To: <200301241934.h0OJYf0V005773@turing-police.cc.vt.edu>
On Fri, Jan 24 2003, Valdis.Kletnieks@vt.edu wrote:
> On Sat, 25 Jan 2003 04:22:39 +1100, Nick Piggin said:
> > We probably wouldn't want to go that far as you obviously can
> > only merge reads with reads and writes with writes, a flag would
> > be fine. We have to get the basics working first though ;)
>
> "obviously can only"? Admittedly, merging reads and writes is a lot
> trickier, and probably "too hairy to bother", but I'm not aware of a
> fundamental "cant" that applies across IDE/SCSI/USB/1394/fiberchannel/etc.
Nicks comment refers to the block layer situation, we obviously cannot
merge reads and writes there. You would basically have to rewrite the
entire request submission structure and break all drivers. And for zero
benefit. Face it, it would be stupid to even attempt such a manuever.
Since you bring it up, you must know if a device which can take a single
command that says "read blocks a to b, and write blocks x to z"? Even if
such a thing existed, it would be much better implemented by the driver
as pulling more requests of the queue and constructing these weirdo
commands itself. Something as ugly as that would never invade the Linux
block layer, at least not as long as I have any input on the design of
it.
So I quite agree with the "obviously".
--
Jens Axboe
--
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-mm.org/
next prev parent reply other threads:[~2003-01-24 20:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:50 2.5.59-mm5 Andrew Morton
2003-01-24 11:03 ` 2.5.59-mm5 Alex Bligh - linux-kernel
2003-01-24 11:16 ` 2.5.59-mm5 Andrew Morton
2003-01-24 11:23 ` 2.5.59-mm5 Alex Tomas
2003-01-24 11:50 ` 2.5.59-mm5 Andrew Morton
2003-01-24 12:05 ` 2.5.59-mm5 Alex Tomas
2003-01-24 19:12 ` 2.5.59-mm5 Andrew Morton
2003-01-24 19:58 ` 2.5.59-mm5 Alex Tomas
2003-01-25 17:32 ` 2.5.59-mm5 Ed Tomlinson
2003-01-25 17:41 ` 2.5.59-mm5 Andrew Morton
2003-01-25 20:34 ` 2.5.59-mm5 Ed Tomlinson
2003-01-25 22:33 ` 2.5.59-mm5 Andrew Morton
2003-01-26 1:43 ` 2.5.59-mm5 Ed Tomlinson
2003-01-26 2:17 ` 2.5.59-mm5 Andrew Morton
2003-01-26 3:51 ` 2.5.59-mm5 Ed Tomlinson
2003-01-26 4:04 ` 2.5.59-mm5 Andrew Morton
2003-01-24 15:56 ` 2.5.59-mm5 Oliver Xymoron
2003-01-24 16:04 ` 2.5.59-mm5 Nick Piggin
2003-01-24 17:09 ` 2.5.59-mm5 Giuliano Pochini
2003-01-24 17:22 ` 2.5.59-mm5 Nick Piggin
2003-01-24 19:34 ` 2.5.59-mm5 Valdis.Kletnieks
2003-01-24 20:04 ` Jens Axboe [this message]
2003-01-24 22:02 ` 2.5.59-mm5 Valdis.Kletnieks
2003-01-25 12:28 ` 2.5.59-mm5 Jens Axboe
2003-01-24 12:14 ` 2.5.59-mm5 Nikita Danilov
2003-01-24 16:00 ` 2.5.59-mm5 Nick Piggin
2003-01-24 11:23 ` 2.5.59-mm5 Jens Axboe
2003-01-24 13:59 ` 2.5.59-mm5 got stuck during boot Helge Hafting
2003-01-24 17:44 ` Ed Tomlinson
2003-01-24 17:56 ` Nick Piggin
2003-01-24 19:18 ` Ed Tomlinson
2003-01-25 8:33 ` 2.5.59-mm5 Andres Salomon
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=20030124200434.GD889@suse.de \
--to=axboe@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oxymoron@waste.org \
--cc=piggin@cyberone.com.au \
--cc=pochini@shiny.it \
/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