From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: DVD blockdevice buffers
Date: Thu, 24 May 2001 00:09:33 +0200 [thread overview]
Message-ID: <20010524000933.A764@athlon.random> (raw)
In-Reply-To: <20010523205748.L8080@redhat.com> <Pine.LNX.4.31.0105231258420.6642-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.31.0105231258420.6642-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, May 23, 2001 at 01:01:56PM -0700
On Wed, May 23, 2001 at 01:01:56PM -0700, Linus Torvalds wrote:
> [..] I assume that Andrea basically
> made the block-size be the same as the page size. That's how I would have
exactly (softblocksize is 4k fixed, regardless of the page cache size to
avoid confusing device drivers).
> done it (and then waited for people to find real life cases where we want
> to allow sector writes).
Correct, the partial write logic is kind of disabled on x86 because the
artificial softblocksize of the blkdev pagecache matches the
pagecachesize but it should just work on the other archs.
Now I can try to make the bh more granular for partial writes in a
dynamic manner (so we don't pay the overhead of the 512byte bh in the
common case) but I think this would need its own additional logic and I
prefer to think about it after I solved the coherency issues between
pinned buffer cache and filesystem, so after the showstoppers are solved
and the patch is just usable in real life (possibly with the overhead of
read-modify-write for some workload doing small random write I/O).
An easy short term fix for removing the read-modify-write would be to use the
hardblocksize of the underlying device as the softblocksize but again
that would cause us to pay for the 512byte bhs which I don't like to... ;)
Andrea
next prev parent reply other threads:[~2001-05-23 22:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 19:02 DVD blockdevice buffers Eduard Hasenleithner
2001-05-18 19:25 ` Jens Axboe
2001-05-18 19:59 ` Eduard Hasenleithner
2001-05-20 2:36 ` Linus Torvalds
2001-05-23 17:34 ` Stephen C. Tweedie
2001-05-23 18:12 ` Linus Torvalds
2001-05-23 19:57 ` Stephen C. Tweedie
2001-05-23 20:01 ` Linus Torvalds
2001-05-23 20:40 ` Jeff Garzik
2001-05-23 22:32 ` Andrea Arcangeli
2001-05-25 20:12 ` blkdev-pagecache-2 [was Re: DVD blockdevice buffers] Andrea Arcangeli
2001-05-25 20:15 ` Andrea Arcangeli
2001-05-23 22:09 ` Andrea Arcangeli [this message]
2001-05-23 22:13 ` DVD blockdevice buffers Alexander Viro
2001-05-23 22:24 ` Andrea Arcangeli
2001-05-24 11:36 ` Stephen C. Tweedie
2001-05-25 15:09 ` Eric W. Biederman
2001-05-25 15:45 ` Stephen C. Tweedie
2001-05-25 17:16 ` Linus Torvalds
2001-05-25 17:40 ` Alexander Viro
2001-05-25 18:05 ` Linus Torvalds
2001-05-25 18:24 ` Alexander Viro
2001-05-25 19:02 ` Stephen C. Tweedie
2001-05-27 6:38 ` Pavel Machek
2001-05-25 21:07 ` Eric W. Biederman
2001-05-25 21:18 ` Linus Torvalds
2001-05-25 22:31 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 18:16 Adam Schrotenboer
2001-05-19 22:56 ` Jens Axboe
2001-05-20 1:55 ` Adam Schrotenboer
2001-05-21 15:44 ` Adam Schrotenboer
2001-05-21 15:47 ` Jens Axboe
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=20010524000933.A764@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--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