From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Fengnan Chang <changfengnan@bytedance.com>
Subject: Re: [PATCH] io_uring: make fallocate be hashed work
Date: Mon, 23 Jun 2025 08:59:05 -0600 [thread overview]
Message-ID: <175069074512.48680.9575841881249533750.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250623110218.61490-1-changfengnan@bytedance.com>
On Mon, 23 Jun 2025 19:02:18 +0800, Fengnan Chang wrote:
> Like ftruncate and write, fallocate operations on the same file cannot
> be executed in parallel, so it is better to make fallocate be hashed
> work.
>
>
Applied, thanks!
[1/1] io_uring: make fallocate be hashed work
commit: 88a80066af1617fab444776135d840467414beb6
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-06-23 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 11:02 [PATCH] io_uring: make fallocate be hashed work Fengnan Chang
2025-06-23 14:59 ` Jens Axboe [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=175069074512.48680.9575841881249533750.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=changfengnan@bytedance.com \
--cc=io-uring@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