mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keoseong Park <keosung.park@samsung.com>
To: Chao Yu <chao@kernel.org>,
	Keoseong Park <keosung.park@samsung.com>,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net" 
	<linux-f2fs-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tanghuan@vivo.com" <tanghuan@vivo.com>,
	"changfengnan@vivo.com" <changfengnan@vivo.com>,
	Daejun Park <daejun7.park@samsung.com>,
	Jinyoung CHOI <j-young.choi@samsung.com>,
	Sung-Jun Park <sungjun07.park@samsung.com>
Subject: RE: Re: [PATCH v2] f2fs: fix to use WHINT_MODE
Date: Tue, 12 Oct 2021 11:16:38 +0900	[thread overview]
Message-ID: <20211012021638epcms2p88d9f7abf1abe4ddb29d314d950b537cb@epcms2p8> (raw)
In-Reply-To: <a59baec0-02cf-28d6-17cd-3ff6dfdf0a01@kernel.org>

Hi Chao,

>On 2021/9/30 8:59, Keoseong Park wrote:
>> Since active_logs can be set to 2 or 4 or NR_CURSEG_PERSIST_TYPE(6),
>> it cannot be set to NR_CURSEG_TYPE(8).
>> That is, whint_mode is always off.
>> 
>> Therefore, the condition is changed from NR_CURSEG_TYPE to NR_CURSEG_PERSIST_TYPE.
>> 
>
>Fixes: d0b9e42ab615 (f2fs: introduce inmem curseg)
>
>> Cc: Chao Yu <chao@kernel.org>
>> Reported-by: Huan Tang <tanghuan@vivo.com>
>> Signed-off-by: Fengnan Chang <changfengnan@vivo.com>
>> Signed-off-by: Keoseong Park <keosung.park@samsung.com>
>
>Reviewed-by: Chao Yu <chao@kernel.org>

Thank you for your review.

Best Regards,
Keoseong

>
>Thanks,
>

      parent reply	other threads:[~2021-10-12  2:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210930005939epcms2p7303bf6f96c824720f824989746491cba@epcms2p7>
2021-09-30  0:59 ` Keoseong Park
2021-10-09  4:24   ` Chao Yu
     [not found]   ` <CGME20210930005939epcms2p7303bf6f96c824720f824989746491cba@epcms2p8>
2021-10-12  2:16     ` Keoseong Park [this message]

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=20211012021638epcms2p88d9f7abf1abe4ddb29d314d950b537cb@epcms2p8 \
    --to=keosung.park@samsung.com \
    --cc=changfengnan@vivo.com \
    --cc=chao@kernel.org \
    --cc=daejun7.park@samsung.com \
    --cc=j-young.choi@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sungjun07.park@samsung.com \
    --cc=tanghuan@vivo.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

all inboxes | Powered by JetHome®