From: Lukas Czerner <lczerner@redhat.com>
To: Vivek Haldar <haldar@google.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: do not normalize block requests from fallocate.
Date: Mon, 16 May 2011 11:39:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1105161135260.3670@dhcp-27-109.brq.redhat.com> (raw)
In-Reply-To: <1305321545-17214-1-git-send-email-haldar@google.com>
On Fri, 13 May 2011, Vivek Haldar wrote:
> Currently, an fallocate request of size slightly larger than a power of
> 2 is turned into two block requests, each a power of 2, with the extra
> blocks pre-allocated for future use. When an application calls
> fallocate, it already has an idea about how large the file may grow so
> there is usually little benefit to reserve extra blocks on the
> preallocation list. This reduces disk fragmentation.
>
> Tested: fsstress. Also verified manually that fallocat'ed files are
> contiguously laid out with this change (whereas without it they begin at
> power-of-2 boundaries, leaving blocks in between). CPU usage of
> fallocate is not appreciably higher. In a tight fallocate loop, CPU
> usage hovers between 5%-8% with this change, and 5%-7% without it.
Hi Vivek,
the patch looks good, but I do not understand why you are introducing
new #define when you can simply use EXT4_MB_HINT_NOPREALLOC and then in
the ext4_ext_map_blocks() just do :
ar.flags |= (flags & EXT4_MB_HINT_NOPREALLOC)
and you do not need to introduce new condition. Am I missing something ?
Thanks!
-Lukas
>
> Signed-off-by: Vivek Haldar <haldar@google.com>
> ---
> fs/ext4/ext4.h | 2 ++
> fs/ext4/extents.c | 5 ++++-
> 2 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 076c5d2..e606d34 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -512,6 +512,8 @@ struct ext4_new_group_data {
> /* Convert extent to initialized after IO complete */
> #define EXT4_GET_BLOCKS_IO_CONVERT_EXT (EXT4_GET_BLOCKS_CONVERT|\
> EXT4_GET_BLOCKS_CREATE_UNINIT_EXT)
> + /* Don't normalize when fallocat'ing */
> +#define EXT4_GET_BLOCKS_NO_NORMALIZE 0x0020
>
> /*
> * Flags used by ext4_free_blocks
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index e363f21..f02dd52 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -3304,6 +3304,8 @@ int ext4_ext_map_blocks(handle_t *handle, struct inode *inode,
> else
> /* disable in-core preallocation for non-regular files */
> ar.flags = 0;
> + if (flags & EXT4_GET_BLOCKS_NO_NORMALIZE)
> + ar.flags |= EXT4_MB_HINT_NOPREALLOC;
> newblock = ext4_mb_new_blocks(handle, &ar, &err);
> if (!newblock)
> goto out2;
> @@ -3549,7 +3551,8 @@ retry:
> break;
> }
> ret = ext4_map_blocks(handle, inode, &map,
> - EXT4_GET_BLOCKS_CREATE_UNINIT_EXT);
> + EXT4_GET_BLOCKS_CREATE_UNINIT_EXT |
> + EXT4_GET_BLOCKS_NO_NORMALIZE);
> if (ret <= 0) {
> #ifdef EXT4FS_DEBUG
> WARN_ON(ret <= 0);
>
--
next prev parent reply other threads:[~2011-05-16 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 21:19 Vivek Haldar
2011-05-16 9:39 ` Lukas Czerner [this message]
2011-05-16 17:18 ` Vivek Haldar
2011-05-17 6:47 ` Lukas Czerner
2011-05-23 1:11 ` Ted Ts'o
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=alpine.LFD.2.00.1105161135260.3670@dhcp-27-109.brq.redhat.com \
--to=lczerner@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=haldar@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®