From: Chi Zhiling <chizhiling@163.com>
To: cem@kernel.org
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Chi Zhiling <chizhiling@kylinos.cn>
Subject: [RFC PATCH 0/2] Implement concurrent buffered write with folio lock
Date: Fri, 25 Apr 2025 18:38:39 +0800 [thread overview]
Message-ID: <20250425103841.3164087-1-chizhiling@163.com> (raw)
From: Chi Zhiling <chizhiling@kylinos.cn>
This is a patch attempting to implement concurrent buffered writes.
The main idea is to use the folio lock to ensure the atomicity of the
write when writing to a single folio, instead of using the i_rwsem.
I tried the "folio batch" solution, which is a great idea, but during
testing, I encountered an OOM issue because the locked folios couldn't
be reclaimed.
So for now, I can only allow concurrent writes within a single block.
The good news is that since we already support BS > PS, we can use a
larger block size to enable higher granularity concurrency.
These ideas come from previous discussions:
https://lore.kernel.org/all/953b0499-5832-49dc-8580-436cf625db8c@163.com/
Chi Zhiling (2):
xfs: Add i_direct_mode to indicate the IO mode of inode
xfs: Enable concurrency when writing within single block
fs/xfs/xfs_file.c | 71 ++++++++++++++++++++++++++++++++++++++++++----
fs/xfs/xfs_inode.h | 6 ++++
2 files changed, 72 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-25 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:38 Chi Zhiling [this message]
2025-04-25 10:38 ` [RFC PATCH 1/2] xfs: Add i_direct_mode to indicate the IO mode of inode Chi Zhiling
2025-04-25 15:12 ` Darrick J. Wong
2025-04-26 1:28 ` Chi Zhiling
2025-04-25 10:38 ` [RFC PATCH 2/2] xfs: Enable concurrency when writing within single block Chi Zhiling
2025-04-25 15:15 ` Darrick J. Wong
2025-04-26 1:34 ` Chi Zhiling
2025-04-30 2:05 ` [RFC PATCH 0/2] Implement concurrent buffered write with folio lock Dave Chinner
2025-04-30 9:03 ` Chi Zhiling
2025-04-30 23:45 ` Dave Chinner
2025-05-01 23:57 ` Chi Zhiling
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=20250425103841.3164087-1-chizhiling@163.com \
--to=chizhiling@163.com \
--cc=cem@kernel.org \
--cc=chizhiling@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox