public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dylan Yudaken <[email protected]>
To: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Cc: <[email protected]>, <[email protected]>,
	Dylan Yudaken <[email protected]>
Subject: [PATCH liburing v2 0/3] 6.0 updates
Date: Tue, 27 Sep 2022 03:21:59 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

liburing updates for 6.0:

Patch 1 updates to account for the single issuer ring being assigned at
ring creation time.
Patch 2 updates man pages from 5.20 -> 6.0
Patch 3 reduces test flakiness

v2:
 - handle IORING_SETUP_R_DISABLED semantics
 - fix unique path in open-direct-pick test 

Dylan Yudaken (3):
  handle single issuer task registration at ring creation
  update documentation to reflect no 5.20 kernel
  give open-direct-pick.c a unique path

 man/io_uring_prep_recv.3    |  2 +-
 man/io_uring_prep_recvmsg.3 |  2 +-
 man/io_uring_setup.2        | 18 +++++++++---------
 test/defer-taskrun.c        |  8 ++++++--
 test/open-direct-pick.c     |  2 +-
 test/single-issuer.c        | 34 ++++++++++++++++++++++++++--------
 6 files changed, 44 insertions(+), 22 deletions(-)


base-commit: 1cba5d6c9e41e2f55ac4c3f93f5e05f9b5082a3e
-- 
2.30.2


             reply	other threads:[~2022-09-27 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 10:21 Dylan Yudaken [this message]
2022-09-27 10:22 ` [PATCH liburing v2 1/3] handle single issuer task registration at ring creation Dylan Yudaken
2022-09-27 10:22 ` [PATCH liburing v2 2/3] update documentation to reflect no 5.20 kernel Dylan Yudaken
2022-09-27 11:02   ` Ammar Faizi
2022-09-27 10:22 ` [PATCH liburing v2 3/3] give open-direct-pick.c a unique path Dylan Yudaken
2022-09-27 11:00   ` Ammar Faizi
2022-09-27 14:15 ` [PATCH liburing v2 0/3] 6.0 updates 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] \
    [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