From: Fengnan Chang via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: Fengnan Chang <changfengnan@vivo.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH v2 0/3] support compressed file write/read amplifiction
Date: Sat, 7 May 2022 16:17:07 +0800 [thread overview]
Message-ID: <20220507081710.117162-1-changfengnan@vivo.com> (raw)
Optimise f2fs_write_cache_pages, and support compressed file write/read
amplifiction accounting.
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 | 15 ++++++++++-----
fs/f2fs/data.c | 40 +++++++++++++++++++++++++++-------------
fs/f2fs/debug.c | 7 +++++--
fs/f2fs/f2fs.h | 40 ++++++++++++++++++++++++++++++++++++++--
4 files changed, 80 insertions(+), 22 deletions(-)
--
2.35.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2022-05-07 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 8:17 Fengnan Chang via Linux-f2fs-devel [this message]
2022-05-07 8:17 ` [f2fs-dev] [PATCH v2 1/3] f2fs: intorduce f2fs_all_cluster_page_ready Fengnan Chang via Linux-f2fs-devel
2022-07-11 9:24 ` Chao Yu
2022-05-07 8:17 ` [f2fs-dev] [PATCH v2 2/3] f2fs: use onstack pages instead of pvec Fengnan Chang via Linux-f2fs-devel
2022-07-11 9:46 ` Chao Yu
2022-05-07 8:17 ` [f2fs-dev] [PATCH v2 3/3] f2fs: support compressed file write/read amplifiction Fengnan Chang via Linux-f2fs-devel
2022-07-10 12:40 ` fengnan chang
2022-07-11 10:10 ` Chao Yu
2022-06-03 2:13 ` [f2fs-dev] [PATCH v2 0/3] " fengnan chang
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=20220507081710.117162-1-changfengnan@vivo.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=changfengnan@vivo.com \
--cc=chao@kernel.org \
--cc=jaegeuk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.