From: Alex Tomas <alex@clusterfs.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] basic delayed allocation in ext4
Date: Thu, 26 Jul 2007 15:50:46 +0400 [thread overview]
Message-ID: <46A88A96.7@clusterfs.com> (raw)
In-Reply-To: <46A88700.2090807@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
>> + /* first, we need to know whether the block is allocated already
>> + * XXX: when the filesystem has a lot of free blocks, we could
>> + * reserve even allocated blocks to save this lookup */
>> + ret = ext4_get_blocks_wrap(NULL, inode, iblock, 1, bh_result, 0,
>> 0);
>> + if (ret >= 0) {
>
>
> I guess this should be (ret > 0)
well, no. it has to catch allocated and non-allocated blocks
(though can be written more clear, probably)
> I was not able to find mpage_da_writepages()..
sorry, it's part of vfs delayed allocation patch, should be on the list now.
thanks, Alex
prev parent reply other threads:[~2007-07-26 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 9:00 [RFC] basic delayed allocation in ext4 Alex Tomas
2007-07-26 11:35 ` Aneesh Kumar K.V
2007-07-26 11:50 ` Alex Tomas [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=46A88A96.7@clusterfs.com \
--to=alex@clusterfs.com \
--cc=aneesh.kumar@linux.vnet.ibm.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.