[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAF=yD-K6g5sJWNxuPM+-V=W2pOrmV8LNSrBv1HjYYFgJ7hmUeg@mail.gmail.com>
Date: Wed, 21 Jun 2017 16:56:05 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Network Development <netdev@...r.kernel.org>
Cc: David Miller <davem@...emloft.net>,
Linux API <linux-api@...r.kernel.org>,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next v2 04/13] sock: add SOCK_ZEROCOPY sockopt
On Wed, Jun 21, 2017 at 4:36 PM, Willem de Bruijn
<willemdebruijn.kernel@...il.com> wrote:
> From: Willem de Bruijn <willemb@...gle.com>
>
> The send call ignores unknown flags. Legacy applications may already
> unwittingly pass MSG_ZEROCOPY. Continue to ignore this flag unless a
> socket opts in to zerocopy.
>
> Introduce socket option SO_ZEROCOPY to enable MSG_ZEROCOPY processing.
> Processes can also query this socket option to detect kernel support
> for the feature. Older kernels will return ENOPROTOOPT.
>
> Signed-off-by: Willem de Bruijn <willemb@...gle.com>
This was not rebased on top of the SO_PEERGROUPS patch. I will send a v3.
Powered by blists - more mailing lists