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 3/4] liburing: add example programs for napi busy poll
Date: Sun, 5 Feb 2023 08:15:19 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sat, Feb 04, 2023 at 04:24:23PM -0800, Stefan Roesch wrote:
> This adds two example programs to test the napi busy poll functionality.
> It consists of a client program and a server program. To get a napi id,
> the client and the server program need to be run on different hosts.
>
> To test the napi busy poll timeout, the -t needs to be specified. A
> reasonable value for the busy poll timeout is 100. By specifying the
> busy poll timeout on the server and the client the best results are
> accomplished.
>
> Signed-off-by: Stefan Roesch <[email protected]>
This version is much better. No more whitespace issues and the CI is all
green.
Acked-by: Ammar Faizi <[email protected]>
--
Ammar Faizi
next prev parent reply other threads:[~2023-02-05 1:15 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
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 [this message]
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 \
[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