All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: [PATCH v2 for-5.13 0/7] ctx wide rsrc nodes
Date: Tue, 23 Mar 2021 15:36:51 +0000	[thread overview]
Message-ID: <cover.1616513699.git.asml.silence@gmail.com> (raw)

The main idea here is to make make rsrc nodes (aka ref nodes) to be per
ctx rather than per rsrc_data, that is a requirement for having multiple
resource types. All the meat to it in 7/7.

Also rsrc API is complicated and too misuse. 1-6 may be considered to
be preps but also together with 7/7 gradually make the API simpler and
so more resilient.

v2: io_rsrc_node_destroy() last rsrc_node on ctx_free()

Pavel Begunkov (7):
  io_uring: name rsrc bits consistently
  io_uring: simplify io_rsrc_node_ref_zero
  io_uring: use rsrc prealloc infra for files reg
  io_uring: encapsulate rsrc node manipulations
  io_uring: move rsrc_put callback into io_rsrc_data
  io_uring: refactor io_queue_rsrc_removal()
  io_uring: ctx-wide rsrc nodes

 fs/io_uring.c | 237 +++++++++++++++++++++-----------------------------
 1 file changed, 97 insertions(+), 140 deletions(-)

-- 
2.24.0


             reply	other threads:[~2021-03-23 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 15:36 Pavel Begunkov [this message]
2021-03-23 15:36 ` [PATCH v2 1/7] io_uring: name rsrc bits consistently Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 2/7] io_uring: simplify io_rsrc_node_ref_zero Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 3/7] io_uring: use rsrc prealloc infra for files reg Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 4/7] io_uring: encapsulate rsrc node manipulations Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 5/7] io_uring: move rsrc_put callback into io_rsrc_data Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 6/7] io_uring: refactor io_queue_rsrc_removal() Pavel Begunkov
2021-03-23 15:36 ` [PATCH v2 7/7] io_uring: ctx-wide rsrc nodes Pavel Begunkov

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 \
    --in-reply-to=cover.1616513699.git.asml.silence@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.