From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org, zzed@cyberdude.com
Subject: Re: [PROBLEM] 2.4.1 can't mount ext2 CD-ROM
Date: Mon, 19 Feb 2001 02:47:04 +0100 [thread overview]
Message-ID: <20010219024704.C8227@suse.de> (raw)
In-Reply-To: <20010218201639.A6593@suse.de> <E14UfJK-00026X-00@the-village.bc.nu>
In-Reply-To: <E14UfJK-00026X-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 19, 2001 at 01:40:16AM +0000
On Mon, Feb 19 2001, Alan Cox wrote:
> > So put 0 and sure anyone can submit I/O on the size that they want.
> > Now the driver has to support padding reads, or gathering data to do
> > a complete block write. This is silly. Sr should support 512b transfers
> > just fine, but only because I added the necessary _hacks_ to support
> > it. sd doesn't right now for instance.
>
> It is silly to be in the block layer, it is silly to be in each file system.
> Perhaps it belongs in the block queueing/handling code or the caches
>
> But it has to go somewhere, and 2.4 right now is unusable on two of my boxes
> with M/O drives.
Reads can be pretty easily padded, but writes are a bit harder. Maybe
push it to some helper before the device queue sees it? For 2.4 the
best sd solution is probably to just make it able to handle these
requests.
--
Jens Axboe
next prev parent reply other threads:[~2001-02-19 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 17:49 [PROBLEM] 2.4.1 can't mount ext2 CD-ROM Andries.Brouwer
2001-02-18 19:16 ` Jens Axboe
2001-02-19 1:40 ` Alan Cox
2001-02-19 1:47 ` Jens Axboe [this message]
2001-02-19 2:02 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 21:11 Andries.Brouwer
2001-02-19 1:43 ` Jens Axboe
2001-02-18 19:34 Andries.Brouwer
2001-02-18 20:49 ` Jens Axboe
2001-02-18 14:26 Jon Forsberg
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=20010219024704.C8227@suse.de \
--to=axboe@suse.de \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zzed@cyberdude.com \
/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