summaryrefslogtreecommitdiff
path: root/rust/alloc/collections/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2026-01-27 21:01:41 -0700
committerJens Axboe <axboe@kernel.dk>2026-01-27 21:06:28 -0700
commit806ae939c41e5da1d94a1e2b31f5702e96b6c3e3 (patch)
tree897e25a79805fc79724361ba4a3e58b7f11097c4 /rust/alloc/collections/git@git.tavy.me:linux.git
parente26f51f6f68749fb5ee6b3b8f7a5a91bf2633e39 (diff)
io_uring/net: don't continue send bundle if poll was required for retry
If a send bundle has picked a bunch of buffers, then it needs to send all of those to be complete. This may require poll arming, if the send buffer ends up being full. Once a send bundle has been poll armed, no further bundles should be attempted. This allows a current bundle to complete even though it needs to go through polling to do so, but it will not allow another bundle to be started once that has happened. Ideally we would abort a bundle if it was only partially sent, but as some parts of it already went out on the wire, this obviously isn't feasible. Not continuing more bundle attempts post encountering a full socket buffer is the second best thing. Cc: stable@vger.kernel.org Fixes: a05d1f625c7a ("io_uring/net: support bundles for send") Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'rust/alloc/collections/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions