From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org
Subject: blkdev-pagecache-2 [was Re: DVD blockdevice buffers]
Date: Fri, 25 May 2001 22:12:51 +0200 [thread overview]
Message-ID: <20010525221251.I9634@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.31.0105231258420.6642-100000@penguin.transmeta.com> <3B0C202E.AA9962AD@mandrakesoft.com> <20010524003220.C764@athlon.random>
In-Reply-To: <20010524003220.C764@athlon.random>; from andrea@suse.de on Thu, May 24, 2001 at 12:32:20AM +0200
On Thu, May 24, 2001 at 12:32:20AM +0200, Andrea Arcangeli wrote:
> userspace. I will try to work on the blkdev patch tomorrow to bring it
> in an usable state.
It seems in an usable state right but it is still very early beta, I
need to recheck the whole thing, I will do that tomorrow, for now it
should get it right the fsck on a ro mount fs and the cache coherency
across multiple inodes all pointing to the same blkdev, it actually
worked without any problem in the first basic tests I did. However I
expect it to corrupt a rw mounted fs if you open the blkdev under it
(the fsck test happens with the fs ro), so while it's in an usable state
it's not ready for public consumation yet. Of course ramdisk is still
totally broken too. The other first round of bugs mentioned in the first
thread should be fixed. The blocksize is still hardwired to 4k, I'll
think about the read-modify-write problem later. About the proposed
readpage API change I think it's not worthwhile for new hardware where
reading 1k or 4k doesn't make relevant difference. Handling partial
I/O seems worthwhile only during writes because a partial write would
otherwise trigger a read-modify-write operation with a synchronous read.
ftp://ftp.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.4.5pre6/blkdev-pagecache-2
Andrea
next prev parent reply other threads:[~2001-05-25 20:13 UTC|newest]
Thread overview: 27+ 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 ` Andrea Arcangeli [this message]
2001-05-25 20:15 ` blkdev-pagecache-2 [was Re: DVD blockdevice buffers] Andrea Arcangeli
2001-05-23 22:09 ` DVD blockdevice buffers Andrea Arcangeli
2001-05-23 22:13 ` 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
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=20010525221251.I9634@athlon.random \
--to=andrea@suse.de \
--cc=jgarzik@mandrakesoft.com \
--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