From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Daeho Jeong <daeho43@gmail.com>,
Daeho Jeong <daehojeong@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: introduce fragment allocation mode mount option
Date: Mon, 20 Sep 2021 15:57:55 -0700 [thread overview]
Message-ID: <YUkR84sklj0SgosC@google.com> (raw)
In-Reply-To: <9f4a2954-e8c9-abc5-5df4-a7cec53433a3@kernel.org>
On 09/12, Chao Yu wrote:
> On 2021/9/11 7:13, Jaegeuk Kim wrote:
> > Wait. Why do we need to add so many options here? I was expecting to see
> > performance difference when getting random segments or random blocks as
> > an extreme case. I don't get the point why we need the middle of those cases.
>
> I guess we can simply the aging test procedure of filesystem by changing a bit
> based on this patch.
My question was on "fragment:fixed_block".
>
> See comments in below thread.
>
> https://lore.kernel.org/lkml/425daf77-8020-26ce-dc9f-019d9a881b78@kernel.org/
>
> Thanks,
next prev parent reply other threads:[~2021-09-20 22:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 17:24 [PATCH v4] f2fs: introduce fragment allocation mode mount option Daeho Jeong
2021-09-02 23:57 ` [f2fs-dev] " Chao Yu
2021-09-03 20:33 ` Daeho Jeong
2021-09-04 3:33 ` Chao Yu
2021-09-04 4:40 ` Daeho Jeong
2021-09-04 6:45 ` Chao Yu
2021-09-07 18:12 ` Daeho Jeong
2021-09-09 23:50 ` Chao Yu
2021-09-10 14:34 ` Daeho Jeong
2021-09-10 15:24 ` Daeho Jeong
2021-09-11 10:42 ` Chao Yu
2021-09-10 23:13 ` Jaegeuk Kim
2021-09-11 23:45 ` [f2fs-dev] " Chao Yu
2021-09-20 22:57 ` Jaegeuk Kim [this message]
2021-09-22 15:23 ` 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=YUkR84sklj0SgosC@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).