public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET 0/8] Add support for IORING_ASYNC_CANCEL_OP
Date: Fri, 23 Jun 2023 10:47:56 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi,

We currently support matching on user_data OR file descriptor, in
conjunction with the ANY/ALL matches we also have.

This series starts by cleaning up the cancelation support a bit,
most notably using a common match handler to avoid duplicating the
matching code in a few different spots.

Then it adds IORING_ASYNC_CANCEL_USERDATA, to explicitly ask for
matching on user_data. This was the only original way to match, but
we since added FD matching. To retain backwards compatability, we
will always match on user_data IFF none of the other key matches are
set (eg FD and OP).

This now allows matching on any set of criteria that the application
wants. It can match on user_data AND fd, for example.

Finally we add support for IORING_ASYNC_CANCEL_OP, which allows
applications to match on the original request opcode as well.

-- 
Jens Axboe



             reply	other threads:[~2023-06-23 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 16:47 Jens Axboe [this message]
2023-06-23 16:47 ` [PATCH 1/8] io_uring/poll: always set 'ctx' in io_cancel_data Jens Axboe
2023-06-23 16:47 ` [PATCH 2/8] io_uring/timeout: " Jens Axboe
2023-06-23 16:47 ` [PATCH 3/8] io_uring/cancel: abstract out request match helper Jens Axboe
2023-06-23 16:48 ` [PATCH 4/8] io_uring/cancel: fix sequence matching for IORING_ASYNC_CANCEL_ANY Jens Axboe
2023-06-23 16:48 ` [PATCH 5/8] io_uring: use cancelation match helper for poll and timeout requests Jens Axboe
2023-06-23 16:48 ` [PATCH 6/8] io_uring/cancel: add IORING_ASYNC_CANCEL_USERDATA Jens Axboe
2023-06-23 16:48 ` [PATCH 7/8] io_uring/cancel: support opcode based lookup and cancelation Jens Axboe
2023-06-23 16:48 ` [PATCH 8/8] io_uring/cancel: wire up IORING_ASYNC_CANCEL_OP for sync cancel 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] \
    /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