linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jens Axboe <axboe@suse.de>
Cc: Nick Piggin <piggin@cyberone.com.au>,
	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 17:02:48 -0500	[thread overview]
Message-ID: <200301242202.h0OM2m0V007374@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 24 Jan 2003 21:04:34 +0100." <20030124200434.GD889@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

On Fri, 24 Jan 2003 21:04:34 +0100, Jens Axboe said:

> 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.

As I *said* - "hairy beyond benefit", not "cant".

> 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
> such thing existed,

They do exist.

IBM mainframe disks (the 3330/50/80 series) are able to do much more than that
in one CCW chain  So it was *quite* possible to even express things like "Go to
this cylinder/track, search for each record that has value XYZ in the 'key'
field, and if found, write value ABC in the data field". (In fact, the DASD I/O
opcodes for CCW chains are Turing-complete).

>                      it would be much better implemented by the driver
> as pulling more requests of the queue and constructing these weirdo

The only operating system I'm aware of that actually uses that stuff is MVS.

> So I quite agree with the "obviously".

My complaint was the confusion of "obviously cant" with "we have decided we
don't want to".

/Valdis

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2003-01-24 22:02 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                   ` 2.5.59-mm5 Jens Axboe
2003-01-24 22:02                     ` Valdis.Kletnieks [this message]
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=200301242202.h0OM2m0V007374@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@digeo.com \
    --cc=axboe@suse.de \
    --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