public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Stefan Roesch <shr@devkernel.io>,
	Facebook Kernel Team <kernel-team@fb.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	Olivier Langlois <olivier@trillion01.com>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev Mailing List <netdev@vger.kernel.org>,
	io-uring Mailing List <io-uring@vger.kernel.org>
Subject: Re: [RFC PATCH v1 1/3] liburing: add api to set napi busy poll timeout
Date: Fri, 4 Nov 2022 04:55:24 +0700	[thread overview]
Message-ID: <478e464b-0dbf-82fb-ce86-8a796019584b@gnuweeb.org> (raw)
In-Reply-To: <20221103204017.670757-2-shr@devkernel.io>

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 <shr@devkernel.io>
> ---
>   src/include/liburing.h          |  3 +++
>   src/include/liburing/io_uring.h |  4 ++++
>   src/register.c                  | 12 ++++++++++++
>   3 files changed, 19 insertions(+)
> 
> diff --git a/src/include/liburing.h b/src/include/liburing.h
> index 12a703f..ef2510e 100644
> --- a/src/include/liburing.h
> +++ b/src/include/liburing.h
> @@ -235,6 +235,9 @@ int io_uring_register_sync_cancel(struct io_uring *ring,
>   int io_uring_register_file_alloc_range(struct io_uring *ring,
>   					unsigned off, unsigned len);
>   
> +int io_uring_register_busy_poll_timeout(struct io_uring *ring, unsigned int to);
> +int io_uring_unregister_busy_poll_timeout(struct io_uring *ring);
> +

If you export a non inline function, you should also update the liburing.map
file.

-- 
Ammar Faizi


  reply	other threads:[~2022-11-03 21:55 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 [this message]
2022-11-07 17:54     ` Stefan Roesch
2022-11-03 22:09   ` Ammar Faizi
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 \
    --in-reply-to=478e464b-0dbf-82fb-ce86-8a796019584b@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olivier@trillion01.com \
    --cc=shr@devkernel.io \
    /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