From: Heming Zhao <heming.zhao@suse.com>
To: joseph.qi@linux.alibaba.com
Cc: Heming Zhao <heming.zhao@suse.com>,
ocfs2-devel@lists.linux.dev, ailiop@suse.com
Subject: [PATCH v4 0/3] improve write IO performance when fragmentation is high
Date: Wed, 27 Mar 2024 16:21:43 +0800 [thread overview]
Message-ID: <20240327082146.6258-1-heming.zhao@suse.com> (raw)
Please ignore previous patches, and using these patches for reviewing.
In v4, I split 3 patch files for easy reviewing:
- (1/3, existing) improve write IO performance when fragmentation is high
- (2/3, new) adjust enabling place for la-window
- (3/3, new) speed up chain-list searching
Heming Zhao (3):
ocfs2: improve write IO performance when fragmentation is high
ocfs2: adjust enabling place for la window
ocfs2: speed up chain-list searching
fs/ocfs2/localalloc.c | 17 ++++---
fs/ocfs2/move_extents.c | 2 +-
fs/ocfs2/ocfs2_fs.h | 3 +-
fs/ocfs2/resize.c | 8 +++
fs/ocfs2/suballoc.c | 110 ++++++++++++++++++++++++++++++++++------
fs/ocfs2/suballoc.h | 6 ++-
6 files changed, 119 insertions(+), 27 deletions(-)
--
2.35.3
next reply other threads:[~2024-03-27 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 8:21 Heming Zhao [this message]
2024-03-27 8:21 ` [PATCH v4 1/3] ocfs2: improve write IO performance when fragmentation is high Heming Zhao
2024-03-27 10:58 ` Joseph Qi
2024-03-27 12:54 ` Heming Zhao
2024-03-28 1:50 ` Joseph Qi
2024-03-28 1:55 ` Heming Zhao
2024-03-27 8:21 ` [PATCH v4 2/3] ocfs2: adjust enabling place for la window Heming Zhao
2024-03-27 11:05 ` Joseph Qi
2024-03-27 12:59 ` Heming Zhao
2024-03-28 1:58 ` Joseph Qi
2024-03-28 2:36 ` Heming Zhao
2024-03-27 8:21 ` [PATCH v4 3/3] ocfs2: speed up chain-list searching Heming Zhao
2024-03-27 11:17 ` Joseph Qi
2024-03-27 12:59 ` Heming Zhao
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=20240327082146.6258-1-heming.zhao@suse.com \
--to=heming.zhao@suse.com \
--cc=ailiop@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=ocfs2-devel@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).