public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, pabeni@redhat.com,
	netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>,
	Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH manpages v2 2/2] udp.7: add UDP_GRO
Date: Mon, 6 Mar 2023 14:37:59 +0100	[thread overview]
Message-ID: <cf3aa207-7423-f04a-ad02-4eda85f58301@gmail.com> (raw)
In-Reply-To: <20230302154808.2139031-2-willemdebruijn.kernel@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1904 bytes --]

Hi Willem, 

On 3/2/23 16:48, Willem de Bruijn wrote:
> 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>

Patch applied.  BTW, it was cmsg(3), not (7) :)

Cheers,

Alex

> 
> ---
> 
> Changes v1->v2
>   - semantic newlines: also break on comma
>   - remove bold: section number following function name
> ---
>  man7/udp.7 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man7/udp.7 b/man7/udp.7
> index 6646c1e96bb0..a350a40da340 100644
> --- a/man7/udp.7
> +++ b/man7/udp.7
> @@ -232,6 +232,20 @@ 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).

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-03-06 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 15:48 [PATCH manpages v2 1/2] udp.7: add UDP_SEGMENT Willem de Bruijn
2023-03-02 15:48 ` [PATCH manpages v2 2/2] udp.7: add UDP_GRO Willem de Bruijn
2023-03-06 11:12   ` Simon Horman
2023-03-06 13:37   ` Alejandro Colomar [this message]
2023-03-06 11:12 ` [PATCH manpages v2 1/2] udp.7: add UDP_SEGMENT Simon Horman
2023-03-06 13:29 ` Alejandro Colomar
2023-03-06 13:30 ` Alejandro Colomar
2023-03-06 13:31   ` Alejandro Colomar
2023-03-06 13:40     ` 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=cf3aa207-7423-f04a-ad02-4eda85f58301@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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