From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andre Hedrick <andre@linux-ide.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: Chipsets, DVD-RAM, and timeouts....
Date: Tue, 2 Jan 2001 15:31:02 +0100 [thread overview]
Message-ID: <20010102153102.E10385@suse.de> (raw)
In-Reply-To: <20010101175005.B1650@suse.de> <E14D8qR-00015A-00@the-village.bc.nu>
In-Reply-To: <E14D8qR-00015A-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Jan 01, 2001 at 05:34:01PM +0000
On Mon, Jan 01 2001, Alan Cox wrote:
> > for FAT etc when reading. Writing is a bit more difficult, as that
> > then turns out to generate a read before we can commit a dirty
> > block. IMO, this type of thing does not belong in the drivers --
> > we should _never_ receive request for < hard block size.
>
> Unfortunately someone ripped the support out from 2.2 to do this, then didnt
> fix it. So right now 2.4 is useless to anyone with an M/O drive.
It wasn't deliberately ripped out, it just vanished when Eric started
his SCSI rewrite in 2.3 :-). For 2.5 I would really like the change
mentioned earlier -- make sure that no block drivers should have to
deal with any request for smaller sector sizes than their hw sector
size. For 2.4, I guess I can apply much the same fix for MO as I did
for CD-ROM.
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 15:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 8:07 Chipsets, DVD-RAM, and timeouts Andre Hedrick
2001-01-01 15:27 ` Jens Axboe
2001-01-01 16:12 ` Alan Cox
2001-01-01 16:50 ` Jens Axboe
2001-01-01 17:34 ` Alan Cox
2001-01-01 22:19 ` Stefan Traby
2001-01-01 22:44 ` Alan Cox
2001-01-02 14:31 ` Jens Axboe [this message]
2001-01-02 18:02 ` Kai Henningsen
2001-01-01 18:13 ` Linus Torvalds
2001-01-01 19:06 ` Andre Hedrick
2001-01-01 19:13 ` Alan Cox
2001-01-01 19:53 ` Andre Hedrick
2001-01-01 20:27 ` Linus Torvalds
2001-01-01 20:32 ` Andre Hedrick
2001-01-02 17:30 ` David Woodhouse
2001-01-02 18:38 ` Hakan Lennestal
2001-01-02 18:42 ` Linus Torvalds
2001-01-02 19:15 ` Hakan Lennestal
2001-01-03 0:46 ` James H. Cloos Jr.
2001-01-02 19:44 ` Andre Hedrick
2001-01-02 19:53 ` Alan Cox
2001-01-02 22:27 ` David Woodhouse
2001-01-02 22:42 ` Dan Hollis
2001-01-02 22:44 ` Linus Torvalds
2001-01-02 22:49 ` Andre Hedrick
2001-01-02 22:56 ` Dan Hollis
2001-01-02 22:50 ` Jens Axboe
2001-01-02 22:59 ` Dan Hollis
2001-01-02 22:59 ` Jens Axboe
2001-01-02 23:48 ` davej
2001-01-05 1:42 ` Hakan Lennestal
2001-01-05 3:42 ` Andre Hedrick
2001-01-03 12:40 ` Zdenek Kabelac
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 15:00 Alex Deucher
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=20010102153102.E10385@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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