public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET v2 0/8] Poll improvements
Date: Fri, 19 Mar 2021 14:35:08 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi,

Here's v2 of the poll improvements planned for 5.13. For a description,
see the v1 posting here:

https://lore.kernel.org/io-uring/[email protected]/

Changes since v1:

- Split poll update into an events and user_data update. Some users like
  to embed fd etc data in the user_data, so makes sense to allow update
  of that too. So we now have POLL_UPDATE_EVENTS and
  POLL_UPDATE_USER_DATA that can be used independently or together.

- Fix missing hangup for some cases.

- Rebase on current 5.13 io_uring tree.

- Various little fixes.

-- 
Jens Axboe



             reply	other threads:[~2021-03-19 20:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 20:35 Jens Axboe [this message]
2021-03-19 20:35 ` [PATCH 1/8] io_uring: mask in error/nval/hangup consistently for poll Jens Axboe
2021-03-19 20:35 ` [PATCH 2/8] io_uring: allocate memory for overflowed CQEs Jens Axboe
2021-03-19 20:35 ` [PATCH 3/8] io_uring: include cflags in completion trace event Jens Axboe
2021-03-19 20:35 ` [PATCH 4/8] io_uring: add multishot mode for IORING_OP_POLL_ADD Jens Axboe
2021-03-19 20:35 ` [PATCH 5/8] io_uring: abstract out helper for removing poll waitqs/hashes Jens Axboe
2021-03-19 20:35 ` [PATCH 6/8] io_uring: terminate multishot poll for CQ ring overflow Jens Axboe
2021-03-19 20:35 ` [PATCH 7/8] io_uring: abstract out a io_poll_find_helper() Jens Axboe
2021-03-19 20:35 ` [PATCH 8/8] io_uring: allow events and user_data update of running poll requests 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