LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Chao Yu <chao.yu@linux.dev>
Subject: Re: [RFC NO MERGE] f2fs: extent cache: support unaligned extent
Date: Wed, 14 Jul 2021 10:27:21 +0800	[thread overview]
Message-ID: <ac39c9af-2ddd-5033-2b64-cb10aadc66a2@kernel.org> (raw)
In-Reply-To: <20210707015815.1978-1-chao@kernel.org>

On 2021/7/7 9:58, Chao Yu wrote:
> Compressed inode may suffer read performance issue due to it can not
> use extent cache, so I propose to add this unaligned extent support
> to improve it.
> 
> Currently, it only works in readonly format f2fs image.
> 
> Unaligned extent: in one compressed cluster, physical block number
> will be less than logical block number, so we add an extra physical
> block length in extent info in order to indicate such extent status.
> 
> The idea is if one whole cluster blocks are contiguous physically,
> once its mapping info was readed at first time, we will cache an
> unaligned (or aligned) extent info entry in extent cache, it expects
> that the mapping info will be hitted when rereading cluster.
> 
> Merge policy:
> - Aligned extents can be merged.
> - Aligned extent and unaligned extent can not be merged.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> 
> I just post this for comments, it passes compiling, w/o any test.
> 
>   fs/f2fs/compress.c     | 25 ++++++++++++
>   fs/f2fs/data.c         | 38 +++++++++++++-----
>   fs/f2fs/extent_cache.c | 90 +++++++++++++++++++++++++++++++++++++-----
>   fs/f2fs/f2fs.h         | 33 +++++++++++++---
>   fs/f2fs/node.c         | 20 ++++++++++
>   5 files changed, 181 insertions(+), 25 deletions(-)

Jaegeuk, any thoughts about this idea?

Thanks,

  reply	other threads:[~2021-07-14  2:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07  1:58 Chao Yu
2021-07-14  2:27 ` Chao Yu [this message]
2021-07-19 18:36 ` Jaegeuk Kim
2021-07-20  0:39   ` Chao Yu
2021-07-29  1:41     ` [f2fs-dev] " Chao Yu
2021-07-30 19:20 ` Jaegeuk Kim
2021-08-01  7:03   ` Chao Yu
2021-08-02 18:03     ` Jaegeuk Kim
2021-08-03  1:07       ` Chao Yu
2021-08-03  1:25         ` Jaegeuk Kim
2021-08-03  1:29           ` Chao Yu
2021-08-03  1:31           ` Chao Yu

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=ac39c9af-2ddd-5033-2b64-cb10aadc66a2@kernel.org \
    --to=chao@kernel.org \
    --cc=chao.yu@linux.dev \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [RFC NO MERGE] f2fs: extent cache: support unaligned extent' \
    /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

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).