From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [PATCHSET for-next 0/2] Flag file systems as supporting parallel dio writes
Date: Tue, 7 Mar 2023 10:20:13 -0700 [thread overview]
Message-ID: <20230307172015.54911-1-axboe@kernel.dk> (raw)
Hi,
This has been on my TODO list for a while, and now that ext4 supports
parallel dio writes as well, time to dust it off and send it out... This
adds an FMODE flag to inform users that a given file supports parallel
dio writes. io_uring can use this to avoid serializing dio writes
upfront, in case it isn't needed. A few details in patch #2, patch 1 does
nothing by itself.
--
Jens Axboe
next reply other threads:[~2023-03-07 17:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:20 Jens Axboe [this message]
2023-03-07 17:20 ` [PATCH 1/2] fs: add FMODE_DIO_PARALLEL_WRITE flag Jens Axboe
2023-04-12 13:40 ` Bernd Schubert
2023-04-12 13:43 ` Bernd Schubert
2023-04-13 7:40 ` Miklos Szeredi
2023-04-13 9:25 ` Bernd Schubert
2023-04-14 5:11 ` Christoph Hellwig
2023-04-14 15:36 ` Darrick J. Wong
2023-04-15 13:15 ` Jens Axboe
2023-04-18 12:42 ` Miklos Szeredi
2023-04-18 12:55 ` Bernd Schubert
2023-04-18 22:13 ` Dave Chinner
2023-04-19 1:28 ` Jens Axboe
2023-04-16 5:54 ` Christoph Hellwig
2023-04-19 1:29 ` Jens Axboe
2023-03-07 17:20 ` [PATCH 2/2] io_uring: avoid hashing O_DIRECT writes if the filesystem doesn't need it Jens Axboe
2023-03-15 17:40 ` [PATCHSET for-next 0/2] Flag file systems as supporting parallel dio writes Jens Axboe
2023-03-16 4:29 ` Darrick J. Wong
2023-03-17 2:53 ` Jens Axboe
2023-04-03 12:24 ` Christian Brauner
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=20230307172015.54911-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.