public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Cc: bpf@vger.kernel.org, Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH v5 5/5] selftests/io_uring: add a bpf io_uring selftest
Date: Wed, 11 Feb 2026 08:22:54 -0700	[thread overview]
Message-ID: <cc018c92-1215-4424-8995-4fd5f318c420@kernel.dk> (raw)
In-Reply-To: <52d39c60d06ee9d02ddb04521382045a6b1d543d.1770818588.git.asml.silence@gmail.com>

On 2/11/26 7:32 AM, Pavel Begunkov wrote:
> +	if (inflight < max_inflight) {
> +		unsigned to_submit = max_inflight - inflight;
> +
> +		to_submit = t_min(to_submit, reqs_to_run);
> +
> +		for (int i = 0; i < to_submit; i++) {
> +			struct io_uring_sqe *sqe = sqes + i;
> +
> +			sqe = &sqes[sq_hdr->tail & (SQ_ENTRIES - 1)];

Nit: assign sqe and immediately reassign.

-- 
Jens Axboe

  reply	other threads:[~2026-02-11 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 14:32 [PATCH io_uring-7.1 v5 0/5] BPF controlled io_uring Pavel Begunkov
2026-02-11 14:32 ` [PATCH v5 1/5] io_uring: introduce callback driven main loop Pavel Begunkov
2026-02-11 14:32 ` [PATCH v5 2/5] io_uring/bpf-ops: implement loop_step with BPF struct_ops Pavel Begunkov
2026-02-11 14:32 ` [PATCH v5 3/5] io_uring/bpf-ops: add kfunc helpers Pavel Begunkov
2026-02-11 14:32 ` [PATCH v5 4/5] io_uring/bpf-ops: implement bpf ops registration Pavel Begunkov
2026-02-11 15:21   ` Jens Axboe
2026-02-11 15:40     ` Pavel Begunkov
2026-02-11 14:32 ` [PATCH v5 5/5] selftests/io_uring: add a bpf io_uring selftest Pavel Begunkov
2026-02-11 15:22   ` Jens Axboe [this message]
2026-02-11 15:24 ` [PATCH io_uring-7.1 v5 0/5] BPF controlled io_uring Jens Axboe
2026-02-11 18:58   ` 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=cc018c92-1215-4424-8995-4fd5f318c420@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=alexei.starovoitov@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=bpf@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox