diff options
| author | Christoph Hellwig <hch@lst.de> | 2026-09-09 09:09:02 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2026-09-14 07:42:09 -0600 |
| commit | a9a7b9e8686da4aba9cf8e9c81097401860107e4 (patch) | |
| tree | 4eadceaaea4e4875f514d73e25cc28948fa85491 /tools/lib/python | |
| parent | 85fa731672d1c62f8c4254a6a47f1960c0fd5b5e (diff) | |
| download | linux-next-a9a7b9e8686da4aba9cf8e9c81097401860107e4.tar.gz linux-next-a9a7b9e8686da4aba9cf8e9c81097401860107e4.zip | |
xfs: add support for lazy direct read bounce buffering
Currently direct I/O reads always bounce buffer the I/O to deal with
the case where userspace is modifying the buffer in-flight while
reading data into it.
This is a very expensive countermeasure for something no sane application
should do, so try to avoid it by reading without a bounce buffer first,
and retrying the read on a checksum failure. This avoids the cost of
bounce buffering for sanely behave applications. For the rare case of
an application regularly modifying in-flight buffers, allow forcing the
always bounce buffer behavior through sysfs. And now that we have that
knob, allow disabling read-side bounce buffering entirely for those who
live fast and dangerous.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Link: https://patch.msgid.link/20260909060924.1102037-14-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
