public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Stefan Roesch <[email protected]>
Cc: Facebook Kernel Team <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Jens Axboe <[email protected]>
Subject: Re: [PATCH v7 2/4] liburing: add documentation for new napi busy polling
Date: Sun, 5 Feb 2023 07:56:43 +0700	[thread overview]
Message-ID: <Y97+ywg/[email protected]> (raw)
In-Reply-To: <[email protected]>

On Sat, Feb 04, 2023 at 04:24:22PM -0800, Stefan Roesch wrote:
> +The
> +.BR io_uring_register_napi (3)
> +function registers the NAPI settings for subsequent operations. The NAPI
> +settings are specified in the structure that is passed in the
> +.I napi
> +parameter. The structure consists of the napi timeout
> +.I busy_poll_to
> +(napi busy poll timeout in us) and
> +.I prefer_busy_poll.

nit: That "period" after "prefer_busy_poll" will be underlined if you
write it that way. It would be better if you write:

   .IR prefer_busy_poll .

so that the dot is not underlined when you open that manpage from a
terminal. But not a big deal..

Reviewed-by: Ammar Faizi <[email protected]>

-- 
Ammar Faizi


  reply	other threads:[~2023-02-05  0:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  0:24 [PATCH v7 0/4] liburing: add api for napi busy poll Stefan Roesch
2023-02-05  0:24 ` [PATCH v7 1/4] liburing: add api to set napi busy poll settings Stefan Roesch
2023-02-05  0:47   ` Ammar Faizi
2023-02-05  0:24 ` [PATCH v7 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2023-02-05  0:56   ` Ammar Faizi [this message]
2023-02-05  0:24 ` [PATCH v7 3/4] liburing: add example programs for napi busy poll Stefan Roesch
2023-02-05  1:15   ` Ammar Faizi
2023-02-05  0:24 ` [PATCH v7 4/4] liburing: update changelog with new feature Stefan Roesch
2023-02-05  1:18   ` Ammar Faizi

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=Y97+ywg/[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