From: Jens Axboe <axboe@kernel.dk>
To: redacherkaoui <redacherkaoui67@gmail.com>, io-uring@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring: document advise SQE field reuse for 64-bit lengths
Date: Mon, 16 Feb 2026 09:23:20 -0700 [thread overview]
Message-ID: <d63ef500-f6ae-46b6-ae3d-03e3c2ec9778@kernel.dk> (raw)
In-Reply-To: <20260216161426.10810-1-redacherkaoui67@gmail.com>
On 2/16/26 9:14 AM, redacherkaoui wrote:
> IORING_OP_FADVISE and IORING_OP_MADVISE reuse SQE fields to
> support 64-bit lengths without extending struct io_uring_sqe.
>
> For IORING_OP_FADVISE, the length is carried in sqe->addr when
> non-zero, with sqe->len providing legacy fallback.
>
> For IORING_OP_MADVISE, the length is carried in sqe->off when
> non-zero, with sqe->len providing legacy fallback.
>
> This differs from the more common addr/off/len interpretation
> used by many other opcodes and can be confusing when constructing
> SQEs manually.
>
> Document the field mapping in the UAPI header to clarify the
> intended behavior and reduce the risk of misuse.
Like I asked you before, what on earth is this patch against?
Stop re-sending the same stuff without answering the question.
--
Jens Axboe
next prev parent reply other threads:[~2026-02-16 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:14 [PATCH] io_uring: document advise SQE field reuse for 64-bit lengths redacherkaoui
2026-02-16 16:23 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-16 11:37 redacherkaoui
2026-02-16 15:17 ` 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=d63ef500-f6ae-46b6-ae3d-03e3c2ec9778@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=redacherkaoui67@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox