linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingming <cmm@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: tytso@mit.edu, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/3] ext4: Drop EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE flag
Date: Wed, 06 Jan 2010 11:50:35 -0800	[thread overview]
Message-ID: <1262807435.17552.27.camel@mingming-laptop> (raw)
In-Reply-To: <1262805762-6862-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

On Thu, 2010-01-07 at 00:52 +0530, Aneesh Kumar K.V wrote:
> We should update reserve space if it is delalloc buffer
> and thtat is indicated by EXT4_GET_BLOCKS_DELALLOC_RESERVE flag.
> So use EXT4_GET_BLOCKS_DELALLOC_RESERVE in place of
> EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE
> 

That's a nice cleanup. With the old name, it confused me a bit on your
first patch where I thought even direct IO gets unnecessary reservation
update.

> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
>  fs/ext4/ext4.h    |    7 ++-----
>  fs/ext4/extents.c |    4 ++--
>  fs/ext4/inode.c   |    8 ++++----
>  3 files changed, 8 insertions(+), 11 deletions(-)
> 
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index b98de17..874d169 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -361,14 +361,11 @@ struct ext4_new_group_data {
>  	   so set the magic i_delalloc_reserve_flag after taking the 
>  	   inode allocation semaphore for */
>  #define EXT4_GET_BLOCKS_DELALLOC_RESERVE	0x0004
> -	/* Call ext4_da_update_reserve_space() after successfully 
> -	   allocating the blocks */
> -#define EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE	0x0008
>  	/* caller is from the direct IO path, request to creation of an
>  	unitialized extents if not allocated, split the uninitialized
>  	extent if blocks has been preallocated already*/
> -#define EXT4_GET_BLOCKS_DIO			0x0010
> -#define EXT4_GET_BLOCKS_CONVERT			0x0020
> +#define EXT4_GET_BLOCKS_DIO			0x0008
> +#define EXT4_GET_BLOCKS_CONVERT			0x0010
>  #define EXT4_GET_BLOCKS_DIO_CREATE_EXT		(EXT4_GET_BLOCKS_DIO|\
>  					 EXT4_GET_BLOCKS_CREATE_UNINIT_EXT)
>  	/* Convert extent to initialized after direct IO complete */
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 3b6ff72..765a482 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -3142,7 +3142,7 @@ out:
>  	 * But fallocate would have already updated quota and block
>  	 * count for this offset. So cancel these reservation
>  	 */
> -	if (flags & EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE)
> +	if (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE)
>  		ext4_da_update_reserve_space(inode, allocated, 0);
> 
>  map_out:
> @@ -3388,7 +3388,7 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
>  	 * Update reserved blocks/metadata blocks after successful
>  	 * block allocation which had been deferred till now.
>  	 */
> -	if (flags & EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE)
> +	if (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE)
>  		ext4_da_update_reserve_space(inode, allocated, 1);
> 
>  	/*
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index 3d1a1d6..fec4ea1 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -1309,7 +1309,7 @@ int ext4_get_blocks(handle_t *handle, struct inode *inode, sector_t block,
>  		 * reserve space here.
>  		 */
>  		if ((retval > 0) &&
> -			(flags & EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE))
> +			(flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE))
>  			ext4_da_update_reserve_space(inode, retval, 1);
>  	}
>  	if (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE)
> @@ -2224,10 +2224,10 @@ static int mpage_da_map_blocks(struct mpage_da_data *mpd)
>  	 * variables are updated after the blocks have been allocated.
>  	 */
>  	new.b_state = 0;
> -	get_blocks_flags = (EXT4_GET_BLOCKS_CREATE |
> -			    EXT4_GET_BLOCKS_DELALLOC_RESERVE);
> +	get_blocks_flags = EXT4_GET_BLOCKS_CREATE ;
>  	if (mpd->b_state & (1 << BH_Delay))
> -		get_blocks_flags |= EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE;
> +		get_blocks_flags |= EXT4_GET_BLOCKS_DELALLOC_RESERVE;
> +
>  	blks = ext4_get_blocks(handle, mpd->inode, next, max_blocks,
>  			       &new, get_blocks_flags);
>  	if (blks < 0) {



  reply	other threads:[~2010-01-06 19:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 19:22 [PATCH 1/3] ext4: Fix quota accounting error with fallocate Aneesh Kumar K.V
2010-01-06 19:22 ` [PATCH 2/3] ext4: Drop EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE flag Aneesh Kumar K.V
2010-01-06 19:50   ` Mingming [this message]
2010-01-06 19:22 ` [PATCH 3/3] ext4: unmap the underlying metadata when allocating blocks via fallocate Aneesh Kumar K.V
2010-01-06 20:20   ` Eric Sandeen
2010-01-14 17:00   ` Eric Sandeen
2010-01-14 18:30     ` [PATCH -V2] " Aneesh Kumar K. V
2010-01-14 19:31       ` Eric Sandeen
2010-01-24 18:24       ` tytso
2010-01-25  5:12         ` Aneesh Kumar K. V
2010-01-25  9:02           ` tytso
2010-01-25 15:43             ` Eric Sandeen
2010-01-25 17:55               ` tytso
2010-01-25 18:21                 ` Aneesh Kumar K. V
2010-01-06 19:47 ` [PATCH 1/3] ext4: Fix quota accounting error with fallocate Mingming
2010-01-13 14:55 ` [PATCH -V2] " 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=1262807435.17552.27.camel@mingming-laptop \
    --to=cmm@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).