From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alex Tomas <alex@clusterfs.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] basic delayed allocation in VFS
Date: Thu, 26 Jul 2007 17:17:27 +0530 [thread overview]
Message-ID: <46A889CF.3030101@linux.vnet.ibm.com> (raw)
In-Reply-To: <46A8628D.6070103@clusterfs.com>
Alex Tomas wrote:
> Good day,
>
> please review ...
>
> thanks, Alex
>
>
> basic delayed allocation in VFS:
>
> * block_prepare_write() can be passed special ->get_block() which
> doesn't allocate blocks, but reserve them and mark bh delayed
> * a filesystem can use mpage_da_writepages() with other ->get_block()
> which doesn't defer allocation. mpage_da_writepages() finds all
> non-allocated blocks and try to allocate them with minimal calls
> to ->get_block(), then submit IO using __mpage_writepage()
>
I missed this patch when looking at the ext4 patches. Can we mark related
patch as [ PATCH 1/2 ] so that we know that another patch is going to follow.
-aneesh
prev parent reply other threads:[~2007-07-26 11:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 8:59 [RFC] basic delayed allocation in VFS Alex Tomas
2007-07-26 10:32 ` Jeff Garzik
2007-07-26 10:35 ` Alex Tomas
2007-07-26 12:05 ` Jeff Garzik
2007-07-26 13:33 ` Alex Tomas
2007-07-27 5:07 ` David Chinner
2007-07-27 7:51 ` Alex Tomas
2007-07-27 12:33 ` Jeff Garzik
2007-07-27 12:42 ` Alex Tomas
2007-07-28 19:56 ` Christoph Hellwig
2007-07-29 9:18 ` David Chinner
2007-07-29 12:09 ` Alex Tomas
2007-07-30 0:29 ` David Chinner
2007-07-27 12:38 ` Alex Tomas
2007-07-28 19:57 ` Christoph Hellwig
2007-07-28 19:53 ` Christoph Hellwig
2007-07-28 19:51 ` Christoph Hellwig
2007-07-28 19:56 ` Alex Tomas
2007-07-29 17:30 ` Andreas Dilger
2007-07-29 17:48 ` Alex Tomas
2007-07-29 19:22 ` Christoph Hellwig
2007-07-29 19:24 ` Christoph Hellwig
2007-07-29 19:51 ` Alex Tomas
2007-07-30 0:28 ` Theodore Tso
2007-07-30 17:49 ` Mingming Cao
2007-07-30 19:43 ` Andrew Morton
2007-07-26 11:47 ` Aneesh Kumar K.V [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=46A889CF.3030101@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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.