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 v6 0/4] improve write IO performance when fragmentation is high
Date: Thu, 28 Mar 2024 20:51:59 +0800 [thread overview]
Message-ID: <20240328125203.20892-1-heming.zhao@suse.com> (raw)
The revision log is written in each patch, below 'Signed-off-by'.
## v6
only patch [4/4] contains code change. For details, see
patch [4/4] revision log.
patch 1-3 are unchanged, only add 'Reviewed-by: Joseph Qi <...>'
## v5
following Joseph's suggestion to use a new patch [4/4] for fixing
sparse warnings.
After this patch, there are 3 warnings left:
```
1.
fs/ocfs2/suballoc.c:2490:17: warning: context imbalance in \
'ocfs2_block_group_clear_bits' - different lock contexts for basic block
2.
fs/ocfs2/dlm/dlmthread.c:241:17: warning: context imbalance in \
'dlm_purge_lockres' - unexpected unlock
fs/ocfs2/dlm/dlmthread.c:286:9: warning: context imbalance in \
'dlm_run_purge_list' - different lock contexts for basic block
3.
fs/ocfs2/dlm/dlmmaster.c: note: in included file:
fs/ocfs2/dlm/dlmcommon.h:1119:9: warning: context imbalance in \
'dlm_reset_mleres_owner' - unexpected unlock
fs/ocfs2/dlm/dlmmaster.c:3337:9: warning: context imbalance in \
'dlm_clean_master_list' - different lock contexts for basic block
```
## v4
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
## v1 v2 v3
see patch 1 revision log.
--------------------------
Heming Zhao (4):
ocfs2: improve write IO performance when fragmentation is high
ocfs2: adjust enabling place for la window
ocfs2: speed up chain-list searching
ocfs2: fix sparse warnings
fs/ocfs2/dlm/dlmdomain.c | 11 ++--
fs/ocfs2/export.c | 12 ++---
fs/ocfs2/inode.c | 2 +
fs/ocfs2/localalloc.c | 15 +++---
fs/ocfs2/move_extents.c | 2 +-
fs/ocfs2/ocfs2_fs.h | 3 +-
fs/ocfs2/refcounttree.c | 2 +-
fs/ocfs2/resize.c | 8 +++
fs/ocfs2/suballoc.c | 111 +++++++++++++++++++++++++++++++++------
fs/ocfs2/suballoc.h | 6 ++-
10 files changed, 133 insertions(+), 39 deletions(-)
--
2.35.3
next reply other threads:[~2024-03-28 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 12:51 Heming Zhao [this message]
2024-03-28 12:52 ` [PATCH v6 1/4] ocfs2: improve write IO performance when fragmentation is high Heming Zhao
2024-03-28 12:52 ` [PATCH v6 2/4] ocfs2: adjust enabling place for la window Heming Zhao
2024-03-28 12:52 ` [PATCH v6 3/4] ocfs2: speed up chain-list searching Heming Zhao
2024-03-28 12:52 ` [PATCH v6 4/4] ocfs2: fix sparse warnings Heming Zhao
2024-03-29 1:00 ` Joseph Qi
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=20240328125203.20892-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).