From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
cmm@us.ibm.com, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem
Date: Thu, 10 Aug 2006 17:00:28 -0400 [thread overview]
Message-ID: <44DB9E6C.9070808@garzik.org> (raw)
In-Reply-To: <20060810132720.4d9fced4.akpm@osdl.org>
Andrew Morton wrote:
> On Thu, 10 Aug 2006 16:13:33 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
>
>> The sooner we kill buffer heads and use submit_bio(), the better :)
>
> A buffer_head is a caching entity and a bio is an IO container. They're
> quite separate concepts.
Yeah, sorry, I meant direct pagecache I/O. I forgot that bio doesn't
handle caching.
> 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.
IMO Al Viro work has shown that you can do pagecache I/O without needing
such a heavyweight system.
Jeff
next prev parent reply other threads:[~2006-08-10 21:01 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 [this message]
2006-08-10 21:11 ` [Ext2-devel] " Alex Tomas
2006-08-10 22:18 ` Andrew Morton
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=44DB9E6C.9070808@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--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