From: Andrew Morton <akpm@osdl.org>
To: Alex Tomas <alex@clusterfs.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-fsdevel@vger.kernel.org, cmm@us.ibm.com,
ext2-devel@lists.sourceforge.net,
Badari Pulavarty <pbadari@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem
Date: Thu, 10 Aug 2006 15:18:13 -0700 [thread overview]
Message-ID: <20060810151813.ae352cd8.akpm@osdl.org> (raw)
In-Reply-To: <m3irl0l2is.fsf@bzzz.home.net>
On Fri, 11 Aug 2006 01:11:23 +0400
Alex Tomas <alex@clusterfs.com> wrote:
> >> A buffer_head is the kernel's sole abstraction of a disk block.
> >> Filesystems use disk blocks a lot, and they need such an abstraction.
>
> JG> IMO Al Viro work has shown that you can do pagecache I/O without needing
> JG> such a heavyweight system.
>
> in delayed allocation patch for ext3 (ontop of extents) we do use
> bio's for data.
As does ext3 with `-o writeback,nobh'.
prev parent reply other threads:[~2006-08-10 22:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1155172622.3161.73.camel@localhost.localdomain>
2006-08-10 6:39 ` [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem Andrew Morton
2006-08-10 16:41 ` Mingming Cao
2006-08-10 16:48 ` Jörn Engel
2006-08-10 18:18 ` Andrew Morton
2006-08-10 20:22 ` Jeff Garzik
2006-08-10 20:33 ` Andrew Morton
2006-08-10 20:52 ` Jeff Garzik
2006-08-10 17:44 ` [Ext2-devel] " Theodore Tso
2006-08-10 18:51 ` Badari Pulavarty
2006-08-10 19:23 ` Andrew Morton
2006-08-10 19:36 ` [Ext2-devel] " Dave Kleikamp
2006-08-10 19:54 ` Andrew Morton
2006-08-10 20:12 ` Jeff Garzik
2006-08-10 20:13 ` Jeff Garzik
2006-08-10 20:27 ` Andrew Morton
2006-08-10 21:00 ` Jeff Garzik
2006-08-10 21:11 ` [Ext2-devel] " Alex Tomas
2006-08-10 22:18 ` Andrew Morton [this message]
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=20060810151813.ae352cd8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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