From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing v2 0/5] ranged file slot alloc
Date: Thu, 30 Jun 2022 08:59:54 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/30/22 8:10 AM, Pavel Begunkov wrote:
> Add helpers and test ranged file slot allocation feature
>
> Pavel Begunkov (5):
> update io_uring.h with file slot alloc ranges
> alloc range helpers
> file-register: fix return codes
> tests: print file-register errors to stderr
> test range file alloc
>
> src/include/liburing.h | 3 +
> src/include/liburing/io_uring.h | 10 ++
> src/liburing.map | 1 +
> src/register.c | 14 ++
> test/file-register.c | 235 +++++++++++++++++++++++++++-----
> 5 files changed, 231 insertions(+), 32 deletions(-)
Looks fine to me, but also needs a man page addition... Trying to do
better here going forward so I don't have to spend days before a
release checking what hasn't been documented, and then also write
everything myself.
I can apply this one as-is, but please do send a man page patch as
well.
--
Jens Axboe
next prev parent reply other threads:[~2022-06-30 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 14:10 [PATCH liburing v2 0/5] ranged file slot alloc Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 1/5] update io_uring.h with file slot alloc ranges Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 2/5] alloc range helpers Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 3/5] file-register: fix return codes Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 4/5] tests: print file-register errors to stderr Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 5/5] test range file alloc Pavel Begunkov
2022-06-30 14:59 ` Jens Axboe [this message]
2022-06-30 16:47 ` [PATCH liburing v2 0/5] ranged file slot alloc 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 \
[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