From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel Kobras <kobras@tat.physik.uni-tuebingen.de>,
linux-kernel@vger.kernel.org
Subject: Re: MO-Drive under 2.4.3
Date: Sun, 22 Apr 2001 04:36:18 +0200 [thread overview]
Message-ID: <20010422043618.C4058@suse.de> (raw)
In-Reply-To: <20010422013738.A520@pelks01.extern.uni-tuebingen.de> <E14r7I2-0004d8-00@the-village.bc.nu>
In-Reply-To: <E14r7I2-0004d8-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Apr 22, 2001 at 12:59:44AM +0100
On Sun, Apr 22 2001, Alan Cox wrote:
> > a) Put in lots of bigblock special case code in FAT;
> > b) teach submit_bh() or generic_make_request() to transparently reblock
> > bhs < hw_blksize and remove most special cases from FAT. Specifically,
> > it ought to stop pretending in sb->s_blocksize to use 2k blocks when
> > the fs is really tied to 512 byte blocks.
> >
> > I tend to favour b), but which one is more likely to be accepted?
>
> Al Viro suggested c) which was to transparently make it a loopback mount of
> the raw device and let a loopback layer do the work.
... which is basically the same thing, in that we need to support writes
< hardware block size to devices. This is never going to be an efficient
mechanism, the read gathering required for a 512b write on a 2048b media
is scary. Think cd-rw 64kB blocksize for write. Ugh.
--
Jens Axboe
next prev parent reply other threads:[~2001-04-22 2:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 8:47 MO-Drive under 2.4.3 Detlev Offenbach
2001-04-13 13:08 ` Alan Cox
2001-04-14 9:45 ` Detlev Offenbach
2001-04-14 14:25 ` Alan Cox
2001-04-14 13:00 ` Daniel Kobras
2001-04-14 14:29 ` Alan Cox
2001-04-21 23:37 ` Daniel Kobras
2001-04-21 23:59 ` Alan Cox
2001-04-22 2:36 ` Jens Axboe [this message]
2001-05-01 16:01 ` Daniel Kobras
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=20010422043618.C4058@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kobras@tat.physik.uni-tuebingen.de \
--cc=linux-kernel@vger.kernel.org \
/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.