From: Stefan Roesch <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Facebook Kernel Team <[email protected]>,
io-uring Mailing List <[email protected]>,
Jens Axboe <[email protected]>
Subject: Re: [PATCH v6 1/4] liburing: add api to set napi busy poll settings
Date: Fri, 03 Feb 2023 13:06:18 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Ammar Faizi <[email protected]> writes:
> On Fri, Feb 03, 2023 at 11:03:07AM -0800, Stefan Roesch wrote:
>> This adds two functions to manage the napi busy poll settings:
>> - io_uring_register_napi
>> - io_uring_unregister_napi
>>
>> Signed-off-by: Stefan Roesch <[email protected]>
>> ---
>> src/include/liburing.h | 3 +++
>> src/include/liburing/io_uring.h | 12 ++++++++++++
>> src/liburing.map | 3 +++
>> src/register.c | 12 ++++++++++++
>> 4 files changed, 30 insertions(+)
>
> We have a new rule. Since commit:
>
> 9e2890d35e9677d8cfc7ac66cdb2d97c48a0b5a2 ("build: add liburing-ffi")
>
> Adding a new exported function should also be reflected in
> liburing-ffi.map.
I'll add it to the next version.
next prev parent reply other threads:[~2023-02-03 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 19:03 [PATCH v6 0/4] liburing: add api for napi busy poll Stefan Roesch
2023-02-03 19:03 ` [PATCH v6 1/4] liburing: add api to set napi busy poll settings Stefan Roesch
2023-02-03 20:19 ` Ammar Faizi
2023-02-03 21:06 ` Stefan Roesch [this message]
2023-02-03 19:03 ` [PATCH v6 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2023-02-03 19:03 ` [PATCH v6 3/4] liburing: add example programs for napi busy poll Stefan Roesch
2023-02-03 20:43 ` Ammar Faizi
2023-02-03 21:14 ` Stefan Roesch
2023-02-03 21:20 ` Ammar Faizi
2023-02-03 19:03 ` [PATCH v6 4/4] liburing: update changelog with new feature Stefan Roesch
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] \
[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