From: Stefan Roesch <[email protected]>
To: <[email protected]>, <[email protected]>,
<[email protected]>, <[email protected]>,
<[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>
Subject: [RFC PATCH v3 00/18] io-uring/xfs: support async buffered writes
Date: Wed, 18 May 2022 16:36:51 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This patch series adds support for async buffered writes when using both
xfs and io-uring. Currently io-uring only supports buffered writes in the
slow path, by processing them in the io workers. With this patch series it is
now possible to support buffered writes in the fast path. To be able to use
the fast path the required pages must be in the page cache, the required locks
in xfs can be granted immediately and no additional blocks need to be read
form disk.
Updating the inode can take time. An optimization has been implemented for
the time update. Time updates will be processed in the slow path. While there
is already a time update in process, other write requests for the same file,
can skip the update of the modification time.
Performance results:
For fio the following results have been obtained with a queue depth of
1 and 4k block size (runtime 600 secs):
sequential writes:
without patch with patch libaio psync
iops: 77k 209k 195K 233K
bw: 314MB/s 854MB/s 790MB/s 953MB/s
clat: 9600ns 120ns 540ns 3000ns
For an io depth of 1, the new patch improves throughput by over three times
(compared to the exiting behavior, where buffered writes are processed by an
io-worker process) and also the latency is considerably reduced. To achieve the
same or better performance with the exisiting code an io depth of 4 is required.
Increasing the iodepth further does not lead to improvements.
In addition the latency of buffered write operations is reduced considerably.
Support for async buffered writes:
To support async buffered writes the flag FMODE_BUF_WASYNC is introduced. In
addition the check in generic_write_checks is modified to allow for async
buffered writes that have this flag set.
Changes to the iomap page create function to allow the caller to specify
the gfp flags. Sets the IOMAP_NOWAIT flag in iomap if IOCB_NOWAIT has been set
and specifies the requested gfp flags.
Adds the iomap async buffered write support to the xfs iomap layer.
Adds async buffered write support to the xfs iomap layer.
Support for async buffered write support and inode time modification
Splits the functions for checking if the file privileges need to be removed in
two functions: check function and a function for the removal of file privileges.
The same split is also done for the function to update the file modification time.
Implement an optimization that while a file modification time is pending other
requests for the same file don't need to wait for the file modification update.
This avoids that a considerable number of buffered async write requests get
punted.
Take the ilock in nowait mode if async buffered writes are enabled and enable
the async buffered writes optimization in io_uring.
Support for write throttling of async buffered writes:
Add a no_wait parameter to the exisiting balance_dirty_pages() function. The
function will return -EAGAIN if the parameter is true and write throttling is
required.
Add a new function called balance_dirty_pages_ratelimited_async() that will be
invoked from iomap_write_iter() if an async buffered write is requested.
Enable async buffered write support in xfs
This enables async buffered writes for xfs.
Testing:
This patch has been tested with xfstests and fio.
Changes:
V3:
- Reformat new code in generic_write_checks_count() to line lengthof 80.
- Remove if condition in __iomap_write_begin to maintain current behavior.
- use GFP_NOWAIT flag in __iomap_write_begin
- rename need_file_remove_privs() function to file_needs_remove_privs()
- rename do_file_remove_privs to __file_remove_privs()
- add kernel documentation to file_remove_privs() function
- rework else if branch in file_remove_privs() function
- add kernel documentation to file_modified() function
- add kernel documentation to file_modified_async() function
- rename err variable in file_update_time to ret
- rename function need_file_update_time() to file_needs_update_time()
- rename function do_file_update_time() to __file_update_time()
- don't move check for FMODE_NOCMTIME in generic helper
- reformat __file_update_time for easier reading
- add kernel documentation to file_update_time() function
- fix if in file_update_time from < to <=
- move modification of inode flags from do_file_update_time to file_modified()
When this function is called, the caller must hold the inode lock.
- 3 new patches from Jan to add new no_wait flag to balance_dirty_pages(),
remove patch 12 from previous series
- Make balance_dirty_pages_ratelimited_flags() a static function
- Add new balance_dirty_pages_ratelimited_async() function
V2:
- Remove atomic allocation
- Use direct write in xfs_buffered_write_iomap_begin()
- Use xfs_ilock_for_iomap() in xfs_buffered_write_iomap_begin()
- Remove no_wait check at the end of xfs_buffered_write_iomap_begin() for
the COW path.
- Pass xfs_inode pointer to xfs_ilock_iocb and rename function to
xfs_lock_xfs_inode
- Replace existing uses of xfs_ilock_iocb with xfs_ilock_xfs_inode
- Use xfs_ilock_xfs_inode in xfs_file_buffered_write()
- Callers of xfs_ilock_for_iomap need to initialize lock mode. This is
required so writes use an exclusive lock
- Split of _balance_dirty_pages() from balance_dirty_pages() and return
sleep time
- Call _balance_dirty_pages() in balance_dirty_pages_ratelimited_flags()
- Move call to balance_dirty_pages_ratelimited_flags() in iomap_write_iter()
to the beginning of the loop
Jan Kara (3):
mm: Move starting of background writeback into the main balancing loop
mm: Move updates of dirty_exceeded into one place
mm: Prepare balance_dirty_pages() for async buffered writes
Stefan Roesch (15):
block: Add check for async buffered writes to generic_write_checks
iomap: Add iomap_page_create_gfp to allocate iomap_pages
iomap: Use iomap_page_create_gfp() in __iomap_write_begin
iomap: Add async buffered write support
xfs: Add iomap async buffered write support
fs: Split off remove_needs_file_privs() __remove_file_privs()
fs: Split off file_needs_update_time and __file_update_time
xfs: Enable async write file modification handling.
fs: Optimization for concurrent file time updates.
xfs: Add async buffered write support
io_uring: Add support for async buffered writes
mm: Add balance_dirty_pages_ratelimited_async() function
iomap: Use balance_dirty_pages_ratelimited_flags in iomap_write_iter
io_uring: Add tracepoint for short writes
xfs: Enable async buffered write support
fs/inode.c | 178 ++++++++++++++++++++++++--------
fs/io_uring.c | 32 +++++-
fs/iomap/buffered-io.c | 71 +++++++++++--
fs/read_write.c | 4 +-
fs/xfs/xfs_file.c | 36 +++----
fs/xfs/xfs_iomap.c | 14 ++-
include/linux/fs.h | 7 ++
include/linux/writeback.h | 1 +
include/trace/events/io_uring.h | 25 +++++
mm/page-writeback.c | 108 ++++++++++++-------
10 files changed, 352 insertions(+), 124 deletions(-)
base-commit: 0cdd776ec92c0fec768c7079331804d3e52d4b27
--
2.30.2
next reply other threads:[~2022-05-18 23:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 23:36 Stefan Roesch [this message]
2022-05-18 23:36 ` [RFC PATCH v3 01/18] block: Add check for async buffered writes to generic_write_checks Stefan Roesch
2022-05-19 8:17 ` Christoph Hellwig
2022-05-20 18:23 ` Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 02/18] iomap: Add iomap_page_create_gfp to allocate iomap_pages Stefan Roesch
2022-05-19 8:18 ` Christoph Hellwig
2022-05-20 18:25 ` Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 03/18] iomap: Use iomap_page_create_gfp() in __iomap_write_begin Stefan Roesch
2022-05-19 8:19 ` Christoph Hellwig
2022-05-20 18:26 ` Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 04/18] iomap: Add async buffered write support Stefan Roesch
2022-05-19 8:25 ` Christoph Hellwig
2022-05-20 18:29 ` Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 05/18] xfs: Add iomap " Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 06/18] fs: Split off remove_needs_file_privs() __remove_file_privs() Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 07/18] fs: Split off file_needs_update_time and __file_update_time Stefan Roesch
2022-05-18 23:36 ` [RFC PATCH v3 08/18] xfs: Enable async write file modification handling Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 09/18] fs: Optimization for concurrent file time updates Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 10/18] xfs: Add async buffered write support Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 11/18] io_uring: Add support for async buffered writes Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 12/18] mm: Move starting of background writeback into the main balancing loop Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 13/18] mm: Move updates of dirty_exceeded into one place Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 14/18] mm: Prepare balance_dirty_pages() for async buffered writes Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 15/18] mm: Add balance_dirty_pages_ratelimited_async() function Stefan Roesch
2022-05-19 8:29 ` Christoph Hellwig
2022-05-19 8:54 ` Jan Kara
2022-05-20 18:32 ` Stefan Roesch
2022-05-20 18:29 ` Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 16/18] iomap: Use balance_dirty_pages_ratelimited_flags in iomap_write_iter Stefan Roesch
2022-05-19 8:32 ` Christoph Hellwig
2022-05-20 18:31 ` Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 17/18] io_uring: Add tracepoint for short writes Stefan Roesch
2022-05-18 23:37 ` [RFC PATCH v3 18/18] xfs: Enable async buffered write support Stefan Roesch
2022-05-19 8:32 ` Christoph Hellwig
2022-05-20 18:32 ` Stefan Roesch
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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