From: Jens Axboe <axboe@kernel.dk>
To: Jacob Thompson <jacobT@beta.pyu.ca>, io-uring@vger.kernel.org
Subject: Re: CQE repeats the first item?
Date: Sun, 5 Oct 2025 14:56:05 -0600 [thread overview]
Message-ID: <ef3a1c2c-f356-4b17-b0bd-2c81acde1462@kernel.dk> (raw)
In-Reply-To: <20251005202115.78998140681@vultr155>
On 10/5/25 2:21 PM, Jacob Thompson wrote:
> I'm doing something wrong and I wanted to know if anyone knows what I
> did wrong from the description I'm using syscalls to call
> io_uring_setup and io_uring_enter. I managed to submit 1 item without
> an issue but any more gets me the first item over and over again. In
> my test I did a memset -1 on cqes and sqes, I memset 0 the first ten
> sqes with different user_data (0x1234 + i), and I used the opcode
> IORING_OP_NOP. I called "io_uring_enter(fd, 10, 0,
> IORING_ENTER_SQ_WAKEUP, 0)" and looked at the cq. Item 11 has the
> user_data as '18446744073709551615' which is correct, but the first 10
> all has user_data be 0x1234 which is weird AF since only one item has
> that user_data and I submited 10 I considered maybe the debugger was
> giving me incorrect values so I tried printing the user data in a
> loop, I have no idea why the first one repeats 10 times. I only called
> enter once
>
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 4660
> Id is 18446744073709551615
You're presumably not updating your side of the CQ ring correctly, see
what liburing does when you call io_uring_cqe_seen(). If that's not it,
then you're probably mishandling something else and an example would be
useful as otherwise I'd just be guessing. There's really not much to go
from in this report.
--
Jens Axboe
next prev parent reply other threads:[~2025-10-05 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 20:21 CQE repeats the first item? Jacob Thompson
2025-10-05 20:56 ` Jens Axboe [this message]
2025-10-05 21:54 ` Jacob Thompson
2025-10-06 1:09 ` Jens Axboe
2025-10-06 1:25 ` Jacob Thompson
2025-10-06 1:31 ` Jens Axboe
2025-10-06 1:36 ` Jens Axboe
2025-10-06 2:01 ` Jacob Thompson
2025-10-06 13:56 ` Jens Axboe
2025-10-06 21:45 ` Jacob Thompson
2025-10-06 21:58 ` Jens Axboe
2025-10-05 22:10 ` Jacob Thompson
2025-10-06 1:10 ` 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 \
--in-reply-to=ef3a1c2c-f356-4b17-b0bd-2c81acde1462@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=jacobT@beta.pyu.ca \
/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