From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET next 0/2] Allow MSG_WAITALL for send/sendmsg
Date: Wed, 20 Apr 2022 19:39:35 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Just like we did for recv/recvmsg, allow MSG_WAITALL to mean that we want
to wait for all the requested data instead of doing a partial completion.
Patch 2 ensures that we can sanely use apoll multiple times, as long as
we're making progress on the IO. This is important to avoid punting to
io-wq if we can avoid it. The gate on already having polled is lifted
if we did transfer some data, which should avoid the initial worry of
why that place was in check - repeatedly non-block retrying and getting
-EAGAIN.
--
Jens Axboe
next reply other threads:[~2022-04-21 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 1:39 Jens Axboe [this message]
2022-04-21 1:39 ` [PATCH 1/2] io_uring: support MSG_WAITALL for IORING_OP_SEND(MSG) Jens Axboe
2022-04-21 1:39 ` [PATCH 2/2] io_uring: allow re-poll if we made progress 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 \
[email protected] \
[email protected] \
[email protected] \
/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