From: Heming Zhao <heming.zhao@suse.com>
To: joseph.qi@linux.alibaba.com
Cc: ocfs2-devel@lists.linux.dev, ailiop@suse.com
Subject: Re: [PATCH 0/3] improve write IO performance when fragmentation is high
Date: Wed, 27 Mar 2024 15:53:15 +0800 [thread overview]
Message-ID: <7f06066a-3b3a-467e-b6c7-a8cd0b7ab277@suse.com> (raw)
In-Reply-To: <20240327060914.2583-1-heming.zhao@suse.com>
Sorry, I forgot add v4 tag and there is a mistake in patch.
I will re-send the v4 patch.
-Heming
On 3/27/24 14:09, Heming Zhao wrote:
> In v4 coding, I found new issues and 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(-)
>
prev parent reply other threads:[~2024-03-27 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 6:09 [PATCH 0/3] improve write IO performance when fragmentation is high Heming Zhao
2024-03-27 6:09 ` [PATCH 1/3] ocfs2: " Heming Zhao
2024-03-27 6:09 ` [PATCH 2/3] ocfs2: adjust enabling place for la window Heming Zhao
2024-03-27 6:09 ` [PATCH 3/3] ocfs2: speed up chain-list searching Heming Zhao
2024-03-27 7:53 ` Heming Zhao [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=7f06066a-3b3a-467e-b6c7-a8cd0b7ab277@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).