From: Shen Feng <shen@cn.fujitsu.com>
To: cmm@us.ibm.com
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Theodore Tso <tytso@mit.edu>,
sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH -v2] ext4: Use inode preallocation with -o noextents
Date: Tue, 17 Jun 2008 17:42:57 +0800 [thread overview]
Message-ID: <48578721.4020205@cn.fujitsu.com> (raw)
In-Reply-To: <4855E0F2.9070207@cn.fujitsu.com>
Shen Feng Wrote:
>
> Mingming Cao Wrote:
>> On Thu, 2008-06-05 at 14:13 +0530, Aneesh Kumar K.V wrote:
>>> On Wed, Jun 04, 2008 at 11:22:20PM -0400, Theodore Tso wrote:
>>>> when I moved this patch to the beginning of the unstable patch queue,
>>>> it didn't apply. When I tried to look at it, my head started
>>>> spinning. The patch applied to the wrong function, apparently,
>>>> because there is so much code duplication "patch" got confused. I
>>>> can't blame it, though, because *I* got confused.
>>>>
>
> ...snip...
>
>>> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
>>> index 09922ae..a810a21 100644
>>> --- a/fs/ext4/mballoc.c
>>> +++ b/fs/ext4/mballoc.c
>>> @@ -4048,7 +4048,7 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
>>> sbi = EXT4_SB(sb);
>>>
>>> if (!test_opt(sb, MBALLOC)) {
>>> - block = ext4_new_blocks_old(handle, ar->inode, ar->goal,
>>> + block = ext4_orlov_new_blocks(handle, ar->inode, ar->goal,
>>> &(ar->len), errp);
>>> return block;
>>> }
>> when we get to ext4_mb_new_blocks, don't we already tested MBALLOC is
>> turned on?
>>
>
> ext4_ext_get_blocks calls ext4_mb_new_blocks. So we have to check this.
> So maybe ext4_ext_get_blocks should call ext4_new_blocks and
> we can remove this check.
>
How about this patch?
I tested it with bonnie++ and ltp fs test using mballoc and nonomballoc
options.
Signed-off-by: Shen Feng <shen@cn.fujitsu.com>
---
fs/ext4/extents.c | 25 +++++++++----------------
fs/ext4/mballoc.c | 6 ------
2 files changed, 9 insertions(+), 22 deletions(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 47929c4..3f6be32 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -2528,7 +2528,8 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
ext4_fsblk_t goal, newblock;
int err = 0, depth, ret;
unsigned long allocated = 0;
- struct ext4_allocation_request ar;
+ ext4_lblk_t lleft, lright;
+ ext4_fsblk_t pleft, pright;
__clear_bit(BH_New, &bh_result->b_state);
ext_debug("blocks %u/%lu requested for inode %u\n",
@@ -2653,12 +2654,12 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
ext4_init_block_alloc_info(inode);
/* find neighbour allocated blocks */
- ar.lleft = iblock;
- err = ext4_ext_search_left(inode, path, &ar.lleft, &ar.pleft);
+ lleft = iblock;
+ err = ext4_ext_search_left(inode, path, &lleft, &pleft);
if (err)
goto out2;
- ar.lright = iblock;
- err = ext4_ext_search_right(inode, path, &ar.lright, &ar.pright);
+ lright = iblock;
+ err = ext4_ext_search_right(inode, path, &lright, &pright);
if (err)
goto out2;
@@ -2685,16 +2686,8 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
allocated = max_blocks;
/* allocate new block */
- ar.inode = inode;
- ar.goal = ext4_ext_find_goal(inode, path, iblock);
- ar.logical = iblock;
- ar.len = allocated;
- if (S_ISREG(inode->i_mode))
- ar.flags = EXT4_MB_HINT_DATA;
- else
- /* disable in-core preallocation for non-regular files */
- ar.flags = 0;
- newblock = ext4_mb_new_blocks(handle, &ar, &err);
+ goal = ext4_ext_find_goal(inode, path, iblock);
+ newblock = ext4_new_blocks(handle, inode, goal, &allocated, &err);
if (!newblock)
goto out2;
ext_debug("allocate new block: goal %llu, found %llu/%lu\n",
@@ -2702,7 +2695,7 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
/* try to insert new extent into found leaf and return */
ext4_ext_store_pblock(&newex, newblock);
- newex.ee_len = cpu_to_le16(ar.len);
+ newex.ee_len = cpu_to_le16(allocated);
if (create == EXT4_CREATE_UNINITIALIZED_EXT) /* Mark uninitialized */
ext4_ext_mark_uninitialized(&newex);
err = ext4_ext_insert_extent(handle, inode, path, &newex);
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index c9900aa..bc82d39 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -4010,12 +4010,6 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
sb = ar->inode->i_sb;
sbi = EXT4_SB(sb);
- if (!test_opt(sb, MBALLOC)) {
- block = ext4_new_blocks_old(handle, ar->inode, ar->goal,
- &(ar->len), errp);
- return block;
- }
next prev parent reply other threads:[~2008-06-17 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 20:34 [PATCH -v2] ext4: Use inode preallocation with -o noextents Aneesh Kumar K.V
2008-06-04 2:23 ` Theodore Tso
2008-06-04 4:01 ` Aneesh Kumar K.V
2008-06-05 3:22 ` Theodore Tso
2008-06-05 8:43 ` Aneesh Kumar K.V
2008-06-05 14:55 ` Mingming Cao
2008-06-05 18:24 ` Andreas Dilger
2008-06-05 18:46 ` Aneesh Kumar K.V
2008-06-06 21:33 ` Mingming Cao
2008-06-11 3:26 ` Shen Feng
2008-06-12 9:34 ` Andreas Dilger
2008-06-12 13:41 ` Eric Sandeen
2008-06-11 3:44 ` Shen Feng
2008-06-16 3:41 ` Shen Feng
2008-06-17 9:42 ` Shen Feng [this message]
2008-06-17 10:48 ` Aneesh Kumar K.V
2008-06-18 1:43 ` Shen Feng
2008-06-05 15:37 ` Theodore Tso
2008-06-05 18:28 ` Andreas Dilger
2008-06-05 19:12 ` Aneesh Kumar K.V
2008-06-05 20:58 ` Andreas Dilger
2008-06-06 16:26 ` Aneesh Kumar K.V
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=48578721.4020205@cn.fujitsu.com \
--to=shen@cn.fujitsu.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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.