From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, anuj1072538@gmail.com,
asml.silence@gmail.com, Anuj Gupta <anuj20.g@samsung.com>
Cc: joshi.k@samsung.com
Subject: Re: [PATCH liburing] test/io_uring_passthrough: enhance vectored I/O test coverage
Date: Thu, 22 May 2025 10:07:09 -0600 [thread overview]
Message-ID: <174793002948.1177667.12828826245226088851.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250522112948.2386-1-anuj20.g@samsung.com>
On Thu, 22 May 2025 16:59:48 +0530, Anuj Gupta wrote:
> This patch improves the vectored io test coverage by ensuring that we
> exercise all three kinds of iovec imports:
> 1. Single segment iovec
> 2. Multi segment iovec, below dynamic allocation threshold
> 3. Multi segment iovec, above dynamic allocation threshold
>
> To support this we adjust the test logic to vary iovcnt appropriately
> across submissions. For fixed vectored I/O support (case 2 and 3), we
> register a single large buffer and slice it into vecs[]. This ensures
> that all iovecs map to valid regions within the registered fixed buffer.
> Additionally buffer allocation is adjusted accordingly, while
> maintaining compatibility with existing non-vectored tests.
>
> [...]
Applied, thanks!
[1/1] test/io_uring_passthrough: enhance vectored I/O test coverage
commit: 296dd55813bb91656752a91dd333825eb759b35e
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-05-22 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250522114649epcas5p26e8ab0fef3ff0d39a64345c3d63f64a2@epcas5p2.samsung.com>
2025-05-22 11:29 ` [PATCH liburing] test/io_uring_passthrough: enhance vectored I/O test coverage Anuj Gupta
2025-05-22 16:07 ` Jens Axboe [this message]
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=174793002948.1177667.12828826245226088851.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.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