public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Anuj gupta <anuj1072538@gmail.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: Anuj Gupta <anuj20.g@samsung.com>,
	io-uring@vger.kernel.org, axboe@kernel.dk,  joshi.k@samsung.com
Subject: Re: [PATCH liburing] test/io_uring_passthrough: add test for vectored fixed-buffers
Date: Wed, 21 May 2025 16:05:24 +0530	[thread overview]
Message-ID: <CACzX3Av3G1K0aoZXDOHjfT=Su6G9D-_RyKWjdMwsNpba8T7CFA@mail.gmail.com> (raw)
In-Reply-To: <7e846c8a-3506-4581-bbc5-fdf9e084a5bf@gmail.com>

> LGTM, it's great to have the test, thanks Anuj. FWIW, that's the
> same way I tested the kernel patch.
>
> Somewhat unrelated questions, is there some particular reason why all
> vectored versions are limited to 1 entry iovec? And why do we even care
> calling io_uring_prep_read/write*() helpers when non of the rw related
> fields set are used by passthrough? i.e. iovec passed in the second half
> of the sqe.

Thanks, Pavel!

Regarding the vectored I/O being limited to 1 iovec — yeah, I kept it
simple initially because the plumbing was easier that way. It’s the same
in test/read-write.c, where vectored calls also use just one iovec. But
I agree, for better coverage, it makes sense to test with multiple
iovecs. I’ll prepare and post a follow-up patch that adds that.

About the use of io_uring_prep_read/write*() helpers — you're right,
they don’t really add much here since the passthrough command handles
the fields directly. I’ll work on a cleanup patch to remove those and
simplify the submission code.

>
> --
> Pavel Begunkov
>

  reply	other threads:[~2025-05-21 10:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250521083658epcas5p2c2d23dbcfac4242343365bb85301c5ea@epcas5p2.samsung.com>
2025-05-21  8:19 ` [PATCH liburing] test/io_uring_passthrough: add test for vectored fixed-buffers Anuj Gupta
2025-05-21  9:42   ` Pavel Begunkov
2025-05-21 10:35     ` Anuj gupta [this message]
2025-05-21 13:08       ` Jens Axboe
2025-05-21 14:20         ` Anuj gupta
2025-05-21 14:24           ` Jens Axboe
2025-05-21 14:05       ` Pavel Begunkov
2025-05-21 14:14         ` Jens Axboe
2025-05-21 14:46           ` Pavel Begunkov
2025-05-21 14:51             ` Jens Axboe
2025-05-21 13:08   ` 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='CACzX3Av3G1K0aoZXDOHjfT=Su6G9D-_RyKWjdMwsNpba8T7CFA@mail.gmail.com' \
    --to=anuj1072538@gmail.com \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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