From: Jan Kara <jack@suse.cz>
To: Zheng Liu <gnehzuil.liu@gmail.com>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 5/9 v4] ext4: track all extent status in extent status tree
Date: Thu, 31 Jan 2013 17:50:55 +0100 [thread overview]
Message-ID: <20130131165055.GF4612@quack.suse.cz> (raw)
In-Reply-To: <1359609477-29845-6-git-send-email-wenqing.lz@taobao.com>
On Thu 31-01-13 13:17:53, Zheng Liu wrote:
> From: Zheng Liu <wenqing.lz@taobao.com>
>
> By recording the phycisal block and status, extent status tree is able
> to track the status of every extents. When we call _map_blocks
> functions to lookup an extent or create a new written/unwritten/delayed
> extent, this extent will be inserted into extent status tree.
>
> We don't load all extents from disk in alloc_inode() because it costs
> too much memory, and if a file is opened and closed frequently it will
> takes too much time to load all extent information. So currently when
> we create/lookup an extent, this extent will be inserted into extent
> status tree. Hence, the extent status tree may not comprehensively
> contain all of the extents found in the file.
>
> Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
> Cc: "Theodore Ts'o" <tytso@mit.edu>
> ---
> fs/ext4/extents.c | 5 +++-
> fs/ext4/file.c | 6 +++--
> fs/ext4/inode.c | 73 ++++++++++++++++++++++++++++++++++++-------------------
> 3 files changed, 56 insertions(+), 28 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index aa9a6d2..d23a654 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2074,7 +2074,7 @@ static int ext4_fill_fiemap_extents(struct inode *inode,
> }
>
> /* This is possible iff next == next_del == EXT_MAX_BLOCKS */
> - if (next == next_del) {
> + if (next == next_del && next_del == EXT_MAX_BLOCKS) {
This doesn't seem to be related, does it?
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index e09c7cf..f0dda2a 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -615,18 +615,27 @@ int ext4_map_blocks(handle_t *handle, struct inode *inode,
> (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE))
> ext4_da_update_reserve_space(inode, retval, 1);
> }
> - if (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE) {
> + if (flags & EXT4_GET_BLOCKS_DELALLOC_RESERVE)
> ext4_clear_inode_state(inode, EXT4_STATE_DELALLOC_RESERVED);
>
> - if (retval > 0 && map->m_flags & EXT4_MAP_MAPPED) {
> - int ret;
> -delayed_mapped:
> - /* delayed allocation blocks has been allocated */
> - ret = ext4_es_remove_extent(inode, map->m_lblk,
> - map->m_len);
> - if (ret < 0)
> - retval = ret;
> - }
> + if (retval > 0) {
> + int ret, status;
> +
> + if (flags & EXT4_GET_BLOCKS_PRE_IO)
> + status = EXTENT_STATUS_UNWRITTEN;
> + else if (flags & EXT4_GET_BLOCKS_CONVERT)
> + status = EXTENT_STATUS_WRITTEN;
> + else if (flags & EXT4_GET_BLOCKS_UNINIT_EXT)
> + status = EXTENT_STATUS_UNWRITTEN;
> + else if (flags & EXT4_GET_BLOCKS_CREATE)
> + status = EXTENT_STATUS_WRITTEN;
> + else
> + BUG_ON(1);
> +
> + ret = ext4_es_insert_extent(inode, map->m_lblk, map->m_len,
> + map->m_pblk, status);
> + if (ret < 0)
> + retval = ret;
Hum, are you sure the extent status will be correct? Won't it be safer to
just use whatever we have in 'map'?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-01-31 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 5:17 [PATCH 0/9 v4] ext4: extent status tree (step2) Zheng Liu
2013-01-31 5:17 ` [PATCH 1/9 v4] ext4: refine extent status tree Zheng Liu
2013-01-31 5:17 ` [PATCH 2/9 v4] ext4: remove EXT4_MAP_FROM_CLUSTER flag Zheng Liu
2013-01-31 5:17 ` [PATCH 3/9 v4] ext4: add physical block and status member into extent status tree Zheng Liu
2013-01-31 5:17 ` [PATCH 4/9 v4] ext4: adjust interfaces of " Zheng Liu
2013-01-31 16:02 ` Jan Kara
2013-02-01 2:51 ` Zheng Liu
2013-01-31 5:17 ` [PATCH 5/9 v4] ext4: track all extent status in " Zheng Liu
2013-01-31 16:50 ` Jan Kara [this message]
2013-02-01 5:33 ` Zheng Liu
2013-02-04 11:27 ` Jan Kara
2013-02-05 3:32 ` Zheng Liu
2013-02-05 12:08 ` Jan Kara
2013-02-05 13:24 ` Zheng Liu
2013-02-05 13:27 ` Jan Kara
2013-01-31 5:17 ` [PATCH 6/9 v4] ext4: lookup block mapping " Zheng Liu
2013-01-31 5:17 ` [PATCH 7/9 v4] ext4: remove single extent cache Zheng Liu
2013-01-31 17:05 ` Jan Kara
2013-02-01 3:08 ` Zheng Liu
2013-01-31 5:17 ` [PATCH 8/9 v4] ext4: adjust some functions for reclaiming extents from extent status tree Zheng Liu
2013-01-31 5:17 ` [PATCH 9/9 v4] ext4: reclaim " Zheng Liu
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=20130131165055.GF4612@quack.suse.cz \
--to=jack@suse.cz \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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 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.