All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	io-uring@vger.kernel.org, linux-block@vger.kernel.org,
	Kevin Wolf <kwolf@redhat.com>
Subject: Re: [PATCH V4 4/8] io_uring: support SQE group
Date: Wed, 24 Jul 2024 15:54:21 +0100	[thread overview]
Message-ID: <cb88fbce-fbae-456e-8f8e-e49202fc7149@gmail.com> (raw)
In-Reply-To: <0fa0c9b9-cfb9-4710-85d0-2f6b4398603c@gmail.com>

On 7/24/24 14:41, Pavel Begunkov wrote:
...> io_free_batch_list() {
>      if (req->flags & GROUP) {
>          if (req_is_member(req)) {
>              req->grp_leader->grp_refs--;
>              if (req->grp_leader->grp_refs == 0) {
>                  req->io_task_work.func = io_req_task_complete;
>                  io_req_task_work_add(req->grp_leader);
>                  // can be done better....
>              }
>              goto free_req;
>          }
>          WARN_ON_ONCE(!req_is_leader());
> 
>          if (!(req->flags & SEEN_FIRST_TIME)) {
>              // already posted it just before coming here
>              req->flags |= SKIP_CQE;
>              // we'll see it again when grp_refs hit 0
>              req->flags |= SEEN_FIRST_TIME;

Forgot queue_group_members() here
  
>              // Don't free the req, we're leaving it alive for now.
>              // req->ref/REQ_F_REFCOUNT will be put next time we get here.
>              return; // or continue
>          }
> 
>          clean_up_request_resources(); // calls back into ublk
>          // and now free the leader
>      }
> 
> free_req:
>      // the rest of io_free_batch_list()
>      if (flags & REQ_F_REFCOUNT) {
>          req_drop_ref();
>          ....
>      }
>      ...
> }

-- 
Pavel Begunkov

  reply	other threads:[~2024-07-24 14:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06  3:09 [PATCH V4 0/8] io_uring: support sqe group and provide group kbuf Ming Lei
2024-07-06  3:09 ` [PATCH V4 1/8] io_uring: add io_link_req() helper Ming Lei
2024-07-06  3:09 ` [PATCH V4 2/8] io_uring: add io_submit_fail_link() helper Ming Lei
2024-07-06  3:09 ` [PATCH V4 3/8] io_uring: add helper of io_req_commit_cqe() Ming Lei
2024-07-06  3:09 ` [PATCH V4 4/8] io_uring: support SQE group Ming Lei
2024-07-22 15:33   ` Pavel Begunkov
2024-07-23 14:34     ` Ming Lei
2024-07-24 13:41       ` Pavel Begunkov
2024-07-24 14:54         ` Pavel Begunkov [this message]
2024-07-25 10:33         ` Ming Lei
2024-07-29 13:58           ` Pavel Begunkov
2024-08-06  8:38             ` Ming Lei
2024-08-06 14:26               ` Ming Lei
2024-08-07  3:26                 ` Ming Lei
2024-07-06  3:09 ` [PATCH V4 5/8] io_uring: support sqe group with members depending on leader Ming Lei
2024-07-06  3:09 ` [PATCH V4 6/8] io_uring: support providing sqe group buffer Ming Lei
2024-07-06  3:09 ` [PATCH V4 7/8] io_uring/uring_cmd: support provide group kernel buffer Ming Lei
2024-07-06  3:09 ` [PATCH V4 8/8] ublk: support provide io buffer Ming Lei
2024-07-19  1:03 ` [PATCH V4 0/8] io_uring: support sqe group and provide group kbuf Ming Lei
2024-07-19 12:49   ` 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=cb88fbce-fbae-456e-8f8e-e49202fc7149@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    /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.