linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz, jeff.liu@oracle.com,
	achender@linux.vnet.ibm.com, adityakali@google.com
Subject: Re: [RFC PATCH V2 2/6] ext4: add a delayed extents tree in inode info
Date: Thu, 29 Sep 2011 14:56:38 +0800	[thread overview]
Message-ID: <4E8416A6.3070302@tao.ma> (raw)
In-Reply-To: <1317272926-13303-3-git-send-email-xiaoqiangnk@gmail.com>

Hi Yongqiang,
On 09/29/2011 01:08 PM, Yongqiang Yang wrote:
> This patch adds a delayed extents tree in inode info, so that
> delayed extents can be look up quickly.  Without the tree
> delayed extents are identified by looking up page cache.
> 
> With the tree, FIEMAP, SEEK_HOLE/DATA, bigalloc and writeout
> path can be optimized a lot.
> 
> Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>
> ---
>  fs/ext4/ext4.h |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index ccfa81f..d3c6b97 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -760,6 +760,8 @@ struct ext4_ext_cache {
>  	__u32		ec_len; /* must be 32bit to return holes */
>  };
>  
> +#include "delayed_extents.h"
> +
>  /*
>   * fourth extended file system inode data in memory
>   */
> @@ -837,6 +839,9 @@ struct ext4_inode_info {
>  	struct list_head i_prealloc_list;
>  	spinlock_t i_prealloc_lock;
>  
> +	/* delayed extents */
> +	struct ext4_de_tree i_de_tree;
> +
Can we integrate this patch with patch 1/6?
I think it would be beneficial for the reviewer to see both the
definition of the structure and the place you put it.

Thanks
Tao
>  	/* ialloc */
>  	ext4_group_t	i_last_alloc_group;
>  


  reply	other threads:[~2011-09-29  6:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  5:08 [RFC V2] ext4: implementation of delayed extent tree Yongqiang Yang
2011-09-29  5:08 ` [RFC PATCH V2 1/6] ext4: add two structures supporting " Yongqiang Yang
2011-09-29  5:08 ` [RFC PATCH V2 2/6] ext4: add a delayed extents tree in inode info Yongqiang Yang
2011-09-29  6:56   ` Tao Ma [this message]
2011-09-29  7:09     ` Yongqiang Yang
2011-09-29  5:08 ` [RFC PATCH V2 3/6] ext4: add operations on delayed extent tree Yongqiang Yang
2011-09-29  8:05   ` Tao Ma
2011-09-29  8:36     ` Yongqiang Yang
2011-09-29  9:40       ` Tao Ma
2011-09-29 13:12         ` Yongqiang Yang
2011-09-29 14:10           ` Tao Ma
2011-09-29  5:08 ` [RFC PATCH V2 4/6] ext4: initialize " Yongqiang Yang
2011-09-29  5:08 ` [RFC PATCH V2 5/6] ext4: let ext4 maintian delayed extent trees Yongqiang Yang
2011-09-29  8:45   ` Amir Goldstein
2011-09-29 14:31   ` Tao Ma
2011-09-30  2:08     ` Yongqiang Yang
2011-09-29  5:08 ` [RFC PATCH V2 6/6] ext4: reimplement fiemap on delayed extent tree Yongqiang Yang
2011-09-29 15:28   ` Jeff liu
2011-09-30  0:54     ` Yongqiang Yang
2011-10-03 16:00   ` Lukas Czerner

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=4E8416A6.3070302@tao.ma \
    --to=tm@tao.ma \
    --cc=achender@linux.vnet.ibm.com \
    --cc=adityakali@google.com \
    --cc=jack@suse.cz \
    --cc=jeff.liu@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=xiaoqiangnk@gmail.com \
    /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).