From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH for-next 2/3] alloc range helpers
Date: Thu, 30 Jun 2022 07:08:13 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <218118e4343c04010e9142e14627a7f580f7bca5.1656580293.git.asml.silence@gmail.com>
On 6/30/22 3:13 AM, Pavel Begunkov wrote:
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
> src/include/liburing.h | 3 +++
> src/register.c | 14 ++++++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/src/include/liburing.h b/src/include/liburing.h
> index bb2fb87..45b4da0 100644
> --- a/src/include/liburing.h
> +++ b/src/include/liburing.h
> @@ -186,6 +186,9 @@ int io_uring_unregister_buf_ring(struct io_uring *ring, int bgid);
> int io_uring_register_sync_cancel(struct io_uring *ring,
> struct io_uring_sync_cancel_reg *reg);
>
> +int io_uring_register_file_alloc_range(struct io_uring *ring,
> + unsigned off, unsigned len);
This should go into liburing.map as well.
--
Jens Axboe
next prev parent reply other threads:[~2022-06-30 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:13 [PATCH for-next 0/3] ranged file slot alloc Pavel Begunkov
2022-06-30 9:13 ` [PATCH for-next 1/3] update io_uring.h with file slot alloc ranges Pavel Begunkov
2022-06-30 9:13 ` [PATCH for-next 2/3] alloc range helpers Pavel Begunkov
2022-06-30 13:08 ` Jens Axboe [this message]
2022-06-30 9:13 ` [PATCH for-next 3/3] test range file alloc Pavel Begunkov
2022-06-30 13:09 ` Jens Axboe
2022-06-30 13:32 ` Ammar Faizi
2022-06-30 14:19 ` Pavel Begunkov
2022-06-30 14:31 ` Ammar Faizi
2022-06-30 15:18 ` Pavel Begunkov
2022-06-30 19:26 ` Eli Schwartz
2022-06-30 20:03 ` Jens Axboe
2022-06-30 14:57 ` Jens Axboe
2022-06-30 9:18 ` [PATCH for-next 0/3] ranged file slot alloc Pavel Begunkov
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] \
/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