From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, alx.manpages@gmail.com,
pabeni@redhat.comm, netdev@vger.kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH manpages 2/2] udp.7: add UDP_GRO
Date: Wed, 1 Mar 2023 16:11:46 -0500 [thread overview]
Message-ID: <20230301211146.1974507-2-willemdebruijn.kernel@gmail.com> (raw)
In-Reply-To: <20230301211146.1974507-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemb@google.com>
UDP_GRO was added in commit e20cf8d3f1f7
("udp: implement GRO for plain UDP sockets.")
$ git describe --contains e20cf8d3f1f7
linux/v5.0-rc1~129^2~379^2~8
Kernel source has example code in tools/testing/selftests/net/udpgro*
Per https://www.kernel.org/doc/man-pages/patches.html,
"Describe how you obtained the information in your patch":
I reviewed the relevant UDP_GRO patches.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
man7/udp.7 | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/man7/udp.7 b/man7/udp.7
index ec16306df605..b4cc06791e47 100644
--- a/man7/udp.7
+++ b/man7/udp.7
@@ -229,6 +229,18 @@ calls by passing it as a
.BR cmsg(7).
A value of zero disables the feature.
This option should not be used in code intended to be portable.
+.TP
+.BR UDP_GRO " (since Linux 5.0)"
+Enables UDP receive offload.
+If enabled, the socket may receive multiple datagrams worth of data as
+a single large buffer, together with a
+.BR cmsg(7)
+that holds the segment size.
+This option is the inverse of segmentation offload.
+It reduces receive cost by handling multiple datagrams worth of data
+as a single large packet in the kernel receive path, even when that
+exceeds MTU.
+This option should not be used in code intended to be portable.
.SS Ioctls
These ioctls can be accessed using
.BR ioctl (2).
--
2.39.2.722.g9855ee24e9-goog
next prev parent reply other threads:[~2023-03-01 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:11 [PATCH manpages 1/2] udp.7: add UDP_SEGMENT Willem de Bruijn
2023-03-01 21:11 ` Willem de Bruijn [this message]
2023-03-01 21:35 ` Alejandro Colomar
2023-03-01 22:22 ` Willem de Bruijn
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=20230301211146.1974507-2-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.comm \
--cc=willemb@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