From: Victor Stewart <v@nametag.social>
To: io-uring@vger.kernel.org, soheil@google.com,
netdev@vger.kernel.org, jannh@google.com
Subject: [PATCH v3] Allow UDP cmsghdrs through io_uring
Date: Sun, 13 Dec 2020 20:43:38 +0000 [thread overview]
Message-ID: <20201213204339.24445-1-v@nametag.social> (raw)
here we go, figured it out. sorry about that.
This patch adds PROTO_CMSG_DATA_ONLY to inet_dgram_ops and inet6_dgram_ops so that UDP_SEGMENT (GSO) and UDP_GRO can be used through io_uring.
GSO and GRO are vital to bring QUIC servers on par with TCP throughputs, and together offer a higher
throughput gain than io_uring alone (rate of data transit
considering), thus io_uring is presently the lesser performance choice.
RE http://vger.kernel.org/lpc_net2018_talks/willemdebruijn-lpc2018-udpgso-paper-DRAFT-1.pdf,
GSO is about +~63% and GRO +~82%.
this patch closes that loophole.
net/ipv4/af_inet.c | 1 +
net/ipv6/af_inet6.c | 1 +
net/socket.c | 8 +++++---
3 files changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2020-12-13 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 20:43 Victor Stewart [this message]
2020-12-13 20:43 ` [PATCH v3] Allow UDP cmsghdrs through io_uring Victor Stewart
2020-12-14 2:22 ` Soheil Hassas Yeganeh
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=20201213204339.24445-1-v@nametag.social \
--to=v@nametag.social \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.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