public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Stefan Roesch <[email protected]>,
	Facebook Kernel Team <[email protected]>
Cc: Jens Axboe <[email protected]>,
	Olivier Langlois <[email protected]>,
	Jakub Kicinski <[email protected]>,
	netdev Mailing List <[email protected]>,
	io-uring Mailing List <[email protected]>
Subject: Re: [RFC PATCH v1 1/3] liburing: add api to set napi busy poll timeout
Date: Fri, 4 Nov 2022 05:09:17 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 11/4/22 3:40 AM, Stefan Roesch wrote:
> This adds the two functions to register and unregister the napi busy
> poll timeout:
> - io_uring_register_busy_poll_timeout
> - io_uring_unregister_busy_poll_timeout
> 
> Signed-off-by: Stefan Roesch <[email protected]>

Also, please update the CHANGELOG file if you add a new feature.
Create a new entry for liburing-2.4 release.

Ref: https://github.com/axboe/liburing/discussions/696#discussioncomment-3962770

-- 
Ammar Faizi


  parent reply	other threads:[~2022-11-03 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 20:40 [RFC PATCH v1 0/3] liburing: add api for napi busy poll timeout Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 1/3] liburing: add api to set " Stefan Roesch
2022-11-03 21:55   ` Ammar Faizi
2022-11-07 17:54     ` Stefan Roesch
2022-11-03 22:09   ` Ammar Faizi [this message]
2022-11-07 17:56     ` Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 2/3] liburing: add documentation for new napi busy polling Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 3/3] liburing: add test programs for napi busy poll Stefan Roesch
2022-11-03 22:04   ` Ammar Faizi
2022-11-07 17:57     ` Stefan Roesch
2022-11-03 22:20   ` Ammar Faizi
2022-11-07 17:58     ` 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] \
    [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