From: Daejun Park <daejun7.park@samsung.com>
To: Yongpeng Yang <yangyongpeng1@oppo.com>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Nayeon Kim <nayeoni.kim@samsung.com>,
Siwoo Jung <siu.jung@samsung.com>,
Seokhwan Kim <sukka.kim@samsung.com>,
Dongjin Kim <dongjin_.kim@samsung.com>,
Daejun Park <daejun7.park@samsung.com>
Subject: RE:(2) [f2fs-dev] [RFC PATCH] f2fs: add support single node section mode
Date: Mon, 10 Jun 2024 12:15:47 +0900 [thread overview]
Message-ID: <20240610031547epcms2p526560bc9d2fd3a5f36615fe645640079@epcms2p5> (raw)
In-Reply-To: <0db07a4a-91da-402e-9601-46b196b8cf1b@oppo.com>
> Hi Daejun,
> 1. It is not compatible with "F2FS_OPTION(sbi).active_logs == 2".
> 2. Once has_enough_free_secs is false, F2FS cannot restore to multi-node
> sections even after has_enough_free_secs becomes true and the filesystem
> is unmounted and remounted. This seems unreasonable.
Hi Yongpeng Yang,
1. Yes, I will modify it so that it only applies when active_log is 6.
2. This technique is effective when utilization is high. Therefore, in my scenario, I assumed that only heavy users would use this option. So I assumed that the free section would not be sufficiently secured even after that.
Futhermore, if a new section is allocated to deactivate a single node whenever there is free space, then soon again insufficient free space may occur, resulting in more unnecessary GC.
Thanks,
Daejun
prev parent reply other threads:[~2024-06-10 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240531074640epcms2p46c3cf8b7cc4e707948ae200115e28e39@epcms2p4>
2024-05-31 7:46 ` Daejun Park
2024-06-03 6:37 ` [f2fs-dev] " Yongpeng Yang
[not found] ` <CGME20240531074640epcms2p46c3cf8b7cc4e707948ae200115e28e39@epcms2p5>
2024-06-10 3:15 ` Daejun 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=20240610031547epcms2p526560bc9d2fd3a5f36615fe645640079@epcms2p5 \
--to=daejun7.park@samsung.com \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nayeoni.kim@samsung.com \
--cc=siu.jung@samsung.com \
--cc=sukka.kim@samsung.com \
--cc=yangyongpeng1@oppo.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®