From: Yangtao Li <frank.li@vivo.com>
To: jaegeuk@kernel.org, chao@kernel.org, qxy65535@gmail.com
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qixiaoyu1@xiaomi.com,
xiongping1@xiaomi.com
Subject: Re: [PATCH] f2fs: Support enhanced hot/cold data separation for f2fs
Date: Tue, 29 Nov 2022 15:49:33 +0800 [thread overview]
Message-ID: <20221129074933.25124-1-frank.li@vivo.com> (raw)
In-Reply-To: <20221128085859.5295-1-qixiaoyu1@xiaomi.com>
Hi qixiaoyu1,
Thanks for your patchset.
Does this patchset have data related to memory and performance impact?
Can you provide scripts or commands for related tests?
Thx,
Yangtao
next prev parent reply other threads:[~2022-11-29 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 8:58 [PATCH 0/5] Support enhanced hot/cold data separation for f2fs qixiaoyu1
2022-11-28 8:58 ` [PATCH 1/5] f2fs: record total data blocks allocated since mount qixiaoyu1
2022-11-29 2:51 ` Jaegeuk Kim
2022-12-05 19:04 ` [f2fs-dev] " Jaegeuk Kim
2022-11-28 8:58 ` [PATCH 2/5] f2fs: implement cache to manager block update frequency per inode qixiaoyu1
2022-11-28 10:44 ` kernel test robot
2022-11-28 8:58 ` [PATCH 3/5] f2fs: add age_extent_cache mount option qixiaoyu1
2022-11-28 8:58 ` [PATCH 4/5] f2fs: update block age info during out of place update qixiaoyu1
2022-11-28 11:14 ` kernel test robot
2022-12-12 3:04 ` kernel test robot
2022-11-28 8:58 ` [PATCH 5/5] f2fs: implement data block seperation with block update frequency qixiaoyu1
2022-11-29 7:49 ` Yangtao Li [this message]
2022-11-29 19:14 [f2fs-dev] [PATCH v3 14/23] f2fs: Convert f2fs_write_cache_pages() to use filemap_get_folios_tag() Matthew Wilcox
2022-11-30 12:48 ` [PATCH] f2fs: Support enhanced hot/cold data separation for f2fs Yangtao Li
2022-11-30 15:18 ` Matthew Wilcox
2022-12-07 20:51 ` Luis Chamberlain
2024-01-25 20:47 ` Matthew Wilcox
2024-01-25 20:54 ` Luis Chamberlain
2024-01-26 21:01 ` Matthew Wilcox
2024-01-26 21:32 ` Luis Chamberlain
2024-01-27 7:05 ` Eric Biggers
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=20221129074933.25124-1-frank.li@vivo.com \
--to=frank.li@vivo.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qixiaoyu1@xiaomi.com \
--cc=qxy65535@gmail.com \
--cc=xiongping1@xiaomi.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;
as well as URLs for NNTP newsgroup(s).