From: Cedric Blancher <[email protected]>
To: Tony Solomonik <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH v5 0/2] io_uring: add support for ftruncate
Date: Wed, 24 Jan 2024 09:52:23 +0100 [thread overview]
Message-ID: <CALXu0UdfZm-UJcPqF5H6+PXPp=DC2SA-QFbB-aVywmMT5X3A6g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Wed, 24 Jan 2024 at 09:33, Tony Solomonik <[email protected]> wrote:
>
> 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 ftruncate_file that truncates a struct file
> io_uring: add support for ftruncate
>
> fs/internal.h | 1 +
> fs/open.c | 53 ++++++++++++++++++-----------------
> 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, 93 insertions(+), 26 deletions(-)
> create mode 100644 io_uring/truncate.c
> create mode 100644 io_uring/truncate.h
>
>
> base-commit: d3fa86b1a7b4cdc4367acacea16b72e0a200b3d7
Also fallocate() to punch holes, aka sparse files, must be implemented
Ced
--
Cedric Blancher <[email protected]>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2024-01-24 8:53 UTC|newest]
Thread overview: 9+ 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 ` Cedric Blancher [this message]
2024-01-24 12:52 ` [PATCH v5 0/2] " Jens Axboe
2024-01-24 13:35 ` Cedric Blancher
2024-01-24 13:42 ` 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='CALXu0UdfZm-UJcPqF5H6+PXPp=DC2SA-QFbB-aVywmMT5X3A6g@mail.gmail.com' \
[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