From: Tony Solomonik <tony.solomonik@gmail.com>
Cc: willy@infradead.org, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, brauner@kernel.org,
Tony Solomonik <tony.solomonik@gmail.com>
Subject: [PATCH v6 0/2] io_uring: add support for ftruncate
Date: Fri, 26 Jan 2024 17:21:16 +0200 [thread overview]
Message-ID: <20240126152118.14201-1-tony.solomonik@gmail.com> (raw)
In-Reply-To: <20240124083301.8661-1-tony.solomonik@gmail.com>
This patch adds support for doing truncate through io_uring, eliminating
the need for applications to roll their own thread pool or offload
mechanism to be able to do non-blocking truncates.
Tony Solomonik (2):
Add do_ftruncate that truncates a struct file
io_uring: add support for ftruncate
fs/internal.h | 1 +
fs/open.c | 57 ++++++++++++++++++-----------------
include/uapi/linux/io_uring.h | 1 +
io_uring/Makefile | 2 +-
io_uring/opdef.c | 10 ++++++
io_uring/truncate.c | 48 +++++++++++++++++++++++++++++
io_uring/truncate.h | 4 +++
7 files changed, 95 insertions(+), 28 deletions(-)
create mode 100644 io_uring/truncate.c
create mode 100644 io_uring/truncate.h
base-commit: d3fa86b1a7b4cdc4367acacea16b72e0a200b3d7
--
2.34.1
next prev parent reply other threads:[~2024-01-26 15:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 8:32 [PATCH v5 0/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-24 8:33 ` [PATCH v5 1/2] Add ftruncate_file that truncates a struct file Tony Solomonik
2024-01-25 17:56 ` Christian Brauner
2024-01-25 18:01 ` Matthew Wilcox
2024-01-24 8:33 ` [PATCH v5 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-24 8:52 ` [PATCH v5 0/2] " Cedric Blancher
2024-01-24 12:52 ` Jens Axboe
2024-01-24 13:35 ` Cedric Blancher
2024-01-24 13:42 ` Jens Axboe
2024-01-26 15:21 ` Tony Solomonik [this message]
2024-01-26 15:21 ` [PATCH v6 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-26 15:34 ` Matthew Wilcox
2024-01-26 15:21 ` [PATCH v6 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-26 15:57 ` [PATCH v7 0/2] " Tony Solomonik
2024-01-26 15:57 ` [PATCH v7 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-28 23:50 ` kernel test robot
2024-01-29 0:50 ` Matthew Wilcox
2024-01-26 15:57 ` [PATCH v7 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-01-29 15:15 ` [PATCH v8 0/2] " Tony Solomonik
2024-01-29 15:15 ` [PATCH v8 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-01-29 15:32 ` Matthew Wilcox
2024-01-29 15:39 ` Christian Brauner
[not found] ` <CAD62OrETm04q5F7ef8fpB5xF_vTKEHfas5W86QEssZ2ozyg0DQ@mail.gmail.com>
2024-02-01 23:20 ` Jens Axboe
2024-02-01 23:54 ` Matthew Wilcox
2024-01-29 15:15 ` [PATCH v8 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-02-02 12:17 ` [PATCH v9 0/2] " Tony Solomonik
2024-02-02 12:17 ` [PATCH v9 1/2] Add do_ftruncate that truncates a struct file Tony Solomonik
2024-02-08 15:07 ` Jens Axboe
2024-02-09 10:22 ` Christian Brauner
2024-02-02 12:17 ` [PATCH v9 2/2] io_uring: add support for ftruncate Tony Solomonik
2024-02-09 16:46 ` [PATCH v9 0/2] " Jens Axboe
[not found] ` <CAD62OrGiBX5YuKr_qRzCXPR5Cx_0Vw3Dei9f95Qww1rL45ejdA@mail.gmail.com>
2024-02-09 16:55 ` Jens Axboe
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=20240126152118.14201-1-tony.solomonik@gmail.com \
--to=tony.solomonik@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).