From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, norman.maurer@googlemail.com
Cc: Norman Maurer <norman_maurer@apple.com>
Subject: Re: [PATCH v3] io_uring/net: Allow to do vectorized send
Date: Wed, 30 Jul 2025 06:21:08 -0600 [thread overview]
Message-ID: <175387806823.286703.10174957893702756372.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250729065952.26646-1-norman_maurer@apple.com>
On Mon, 28 Jul 2025 20:59:53 -1000, norman.maurer@googlemail.com wrote:
> At the moment you have to use sendmsg for vectorized send.
> While this works it's suboptimal as it also means you need to
> allocate a struct msghdr that needs to be kept alive until a
> submission happens. We can remove this limitation by just
> allowing to use send directly.
>
>
> [...]
Applied, thanks!
[1/1] io_uring/net: Allow to do vectorized send
commit: 423a72545c7b59f304781bf38050d537b6a7ed5e
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-07-30 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 6:59 [PATCH v3] io_uring/net: Allow to do vectorized send norman.maurer
2025-07-29 12:15 ` Jens Axboe
2025-07-29 17:00 ` Norman Maurer
2025-07-30 12:21 ` 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=175387806823.286703.10174957893702756372.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=norman.maurer@googlemail.com \
--cc=norman_maurer@apple.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