[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210122200723.50e4afe6@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 22 Jan 2021 20:07:23 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Arjun Roy <arjunroy.kdev@...il.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, arjunroy@...gle.com,
edumazet@...gle.com, soheil@...gle.com
Subject: Re: [net-next v2 2/2] tcp: Add receive timestamp support for
receive zerocopy.
On Wed, 20 Jan 2021 16:41:48 -0800 Arjun Roy wrote:
> diff --git a/include/uapi/linux/tcp.h b/include/uapi/linux/tcp.h
> index 768e93bd5b51..b216270105af 100644
> --- a/include/uapi/linux/tcp.h
> +++ b/include/uapi/linux/tcp.h
> @@ -353,5 +353,9 @@ struct tcp_zerocopy_receive {
> __u64 copybuf_address; /* in: copybuf address (small reads) */
> __s32 copybuf_len; /* in/out: copybuf bytes avail/used or error */
> __u32 flags; /* in: flags */
> + __u64 msg_control; /* ancillary data */
> + __u64 msg_controllen;
> + __u32 msg_flags;
> + /* __u32 hole; Next we must add >1 u32 otherwise length checks fail. */
Well, let's hope nobody steps on this landmine.. :)
Applied, thanks!
Powered by blists - more mailing lists