From: Namjae Jeon <linkinjeon@gmail.com>
To: jaegeuk.kim@samsung.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 5/9 v2] f2fs: change GC bitmaps to apply the section granularity
Date: Wed, 3 Apr 2013 17:21:52 +0900 [thread overview]
Message-ID: <CAKYAXd-7J3h4n8hDPLfkSLv+Yht+9kWn9QJCbrv20-D0cx3J-w@mail.gmail.com> (raw)
In-Reply-To: <1364976415.4353.9.camel@kjgkr>
2013/4/3, Jaegeuk Kim <jaegeuk.kim@samsung.com>:
> Hi,
> Agreed, and resolved all the issues like below.
> Thanks,
>
> change log from v1:
> o change local variable position
> o change function shape
> o add NULL_SECNO
>
> From f1802031a467751df6475bd3f56300137fd2ac34 Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> Date: Sun, 31 Mar 2013 13:26:03 +0900
> Subject: [PATCH] f2fs: change GC bitmaps to apply the section
> granularity
> Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
> linux-f2fs-devel@lists.sourceforge.net
>
> This patch removes a bitmap for victim segments selected by foreground
> GC, and
> modifies the other bitmap for victim segments selected by background GC.
>
> 1) foreground GC bitmap
> : We don't need to manage this, since we just only one previous victim
> section
> number instead of the whole victim history.
> The f2fs uses the victim section number in order not to allocate
> currently
> GC'ed section to current active logs.
>
> 2) background GC bitmap
> : This bitmap is used to avoid selecting victims repeatedly by
> background GCs.
> In addition, the victims are able to be selected by foreground GCs,
> since
> there is no need to read victim blocks during foreground GCs.
>
> By the fact that the foreground GC reclaims segments in a section
> unit, it'd
> be better to manage this bitmap based on the section granularity.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Looks good to me!
Reviewed-by: Namjae Jeon <namjae.jeon@samsung.com>
Thanks.
> ---
next prev parent reply other threads:[~2013-04-03 8:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 6:55 [PATCH 1/9] f2fs: do not use duplicate names in a macro Jaegeuk Kim
2013-04-01 6:55 ` [PATCH 2/9] f2fs: introduce TOTAL_SECS macro Jaegeuk Kim
2013-04-03 1:17 ` Namjae Jeon
2013-04-01 6:55 ` [PATCH 3/9] f2fs: remove redundant lock_page calls Jaegeuk Kim
2013-04-03 5:58 ` Namjae Jeon
2013-04-03 8:12 ` [PATCH 3/9 v2] " Jaegeuk Kim
2013-04-03 8:27 ` Namjae Jeon
2013-04-01 6:55 ` [PATCH 4/9] f2fs: allocate new segment aligned with sections Jaegeuk Kim
2013-04-03 6:00 ` Namjae Jeon
2013-04-01 6:55 ` [PATCH 5/9] f2fs: change GC bitmaps to apply the section granularity Jaegeuk Kim
2013-04-03 5:46 ` Namjae Jeon
2013-04-03 8:06 ` [PATCH 5/9 v2] " Jaegeuk Kim
2013-04-03 8:21 ` Namjae Jeon [this message]
2013-04-01 6:55 ` [PATCH 6/9] f2fs: check completion of foreground GC Jaegeuk Kim
2013-04-03 5:54 ` Namjae Jeon
2013-04-01 6:55 ` [PATCH 7/9] f2fs: allocate remained free segments in the LFS mode Jaegeuk Kim
2013-04-03 5:59 ` Namjae Jeon
2013-04-01 6:55 ` [PATCH 8/9] f2fs: avoid race for summary information Jaegeuk Kim
2013-04-03 5:54 ` Namjae Jeon
2013-04-01 6:56 ` [PATCH 9/9] f2fs: fix the bitmap consistency of dirty segments Jaegeuk Kim
2013-04-03 1:14 ` Namjae Jeon
2013-04-03 1:15 ` [PATCH 1/9] f2fs: do not use duplicate names in a macro Namjae Jeon
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=CAKYAXd-7J3h4n8hDPLfkSLv+Yht+9kWn9QJCbrv20-D0cx3J-w@mail.gmail.com \
--to=linkinjeon@gmail.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).