public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: David Wei <[email protected]>, Pavel Begunkov <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v3 0/2] liburing: multishot timeout support
Date: Tue, 18 Apr 2023 19:43:53 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 4/14/23 4:55?PM, David Wei wrote:
> Changes on the liburing side to support multishot timeouts.
> 
> Changes since v2:
> 
> * Edited man page for io_uring_prep_timeout.3
> 
> David Wei (2):
>   liburing: add multishot timeout support
>   liburing: update man page for multishot timeouts
> 
>  man/io_uring_prep_timeout.3     |   7 +
>  src/include/liburing/io_uring.h |   1 +
>  test/timeout.c                  | 263 ++++++++++++++++++++++++++++++++
>  3 files changed, 271 insertions(+)

I applied this, but there's an issue in that the tests don't just skip
if the kernel doesn't support multishot. Tests for liburing need to
accept that the feature isn't available on older kernels. Generally this
is done by the first test setting 'no_timeout_mshot = true' or something
like that, and then subsequent ones just returning T_SETUP_SKIP if
no_timeout_mshot == true and whatever calls the test not failing if
T_SETUP_SKIP is returned.

Would be great if you could send a followup patch against the current
liburing -git that does that. Thanks!

-- 
Jens Axboe


  parent reply	other threads:[~2023-04-19  1:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 22:55 [PATCH v3 0/2] liburing: multishot timeout support David Wei
2023-04-14 22:55 ` [PATCH v3 1/2] liburing: add " David Wei
2023-04-14 22:55 ` [PATCH v3 2/2] liburing: update man page for multishot timeouts David Wei
2023-04-19  1:43 ` Jens Axboe [this message]
2023-04-19 18:56   ` [PATCH v3 0/2] liburing: multishot timeout support David Wei
2023-04-19  2:16 ` Jens Axboe

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] \
    /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