From: Chao Yu <chao@kernel.org>
To: Fengnan Chang <fengnanchang@gmail.com>, jaegeuk@kernel.org
Cc: Fengnan Chang <changfengnan@vivo.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 0/3] support compressed file write/read amplifiction
Date: Sun, 24 Jul 2022 17:36:25 +0800 [thread overview]
Message-ID: <095ae0c1-ca6a-7c71-360a-883dad84a18c@kernel.org> (raw)
In-Reply-To: <20220717053207.192372-1-fengnanchang@gmail.com>
On 2022/7/17 13:32, Fengnan Chang wrote:
> From: Fengnan Chang <changfengnan@vivo.com>
>
> Optimise f2fs_write_cache_pages, and support compressed file write/read
> amplifiction accounting.
It needs to describe what v3 updates?
Thanks,
>
> Fengnan Chang (3):
> f2fs: intorduce f2fs_all_cluster_page_ready
> f2fs: use onstack pages instead of pvec
> f2fs: support compressed file write/read amplifiction
>
> fs/f2fs/compress.c | 21 +++++++++++++++------
> fs/f2fs/data.c | 46 ++++++++++++++++++++++++++++++++--------------
> fs/f2fs/debug.c | 7 +++++--
> fs/f2fs/f2fs.h | 40 ++++++++++++++++++++++++++++++++++++++--
> 4 files changed, 90 insertions(+), 24 deletions(-)
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-07-24 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 5:32 [f2fs-dev] [PATCH v3 0/3] support compressed file write/read amplifiction Fengnan Chang
2022-07-17 5:32 ` [f2fs-dev] [PATCH v3 1/3] f2fs: intorduce f2fs_all_cluster_page_ready Fengnan Chang
2022-07-24 9:33 ` Chao Yu
2022-07-17 5:32 ` [f2fs-dev] [PATCH v3 2/3] f2fs: use onstack pages instead of pvec Fengnan Chang
2022-07-17 5:32 ` [f2fs-dev] [PATCH v3 3/3] f2fs: support compressed file write/read amplifiction Fengnan Chang
2022-07-24 9:58 ` Chao Yu
2022-07-25 13:00 ` fengnan chang
2022-07-24 9:36 ` Chao Yu [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=095ae0c1-ca6a-7c71-360a-883dad84a18c@kernel.org \
--to=chao@kernel.org \
--cc=changfengnan@vivo.com \
--cc=fengnanchang@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).