From: Daniel Borkmann <daniel@iogearbox•net>
To: Willem de Bruijn <willemb@google•com>, netdev@vger•kernel.org
Cc: davem@davemloft•net, edumazet@google•com, ast@plumgrid•com
Subject: Re: [PATCH net-next v2 1/4] packet: add classic BPF fanout mode
Date: Sun, 16 Aug 2015 11:15:08 +0200 [thread overview]
Message-ID: <55D0549C.5040104@iogearbox.net> (raw)
In-Reply-To: <1439605897-28311-2-git-send-email-willemb@google.com>
On 08/15/2015 04:31 AM, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google•com>
>
> Add fanout mode PACKET_FANOUT_CBPF that accepts a classic BPF program
> to select a socket.
>
> This avoids having to keep adding special case fanout modes. One
> example use case is application layer load balancing. The QUIC
> protocol, for instance, encodes a connection ID in UDP payload.
>
> Also add socket option SOL_PACKET/PACKET_FANOUT_DATA that updates data
> associated with the socket group. Fanout mode PACKET_FANOUT_CBPF is the
> only user so far.
>
> Signed-off-by: Willem de Bruijn <willemb@google•com>
Patch looks good to me as well (sorry for the lag, on travel).
Thanks Willem!
Acked-by: Daniel Borkmann <daniel@iogearbox•net>
next prev parent reply other threads:[~2015-08-16 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 2:31 [PATCH net-next v2 0/4] packet: add cBPF and eBPF fanout modes Willem de Bruijn
2015-08-15 2:31 ` [PATCH net-next v2 1/4] packet: add classic BPF fanout mode Willem de Bruijn
2015-08-16 4:58 ` Alexei Starovoitov
2015-08-16 9:15 ` Daniel Borkmann [this message]
2015-08-17 14:29 ` Eric Dumazet
2015-08-15 2:31 ` [PATCH net-next v2 2/4] packet: add extended " Willem de Bruijn
2015-08-16 4:58 ` Alexei Starovoitov
2015-08-16 9:15 ` Daniel Borkmann
2015-08-15 2:31 ` [PATCH net-next v2 3/4] selftests/net: test classic bpf " Willem de Bruijn
2015-08-15 2:31 ` [PATCH net-next v2 4/4] selftests/net: test extended BPF " Willem de Bruijn
2015-08-17 21:23 ` [PATCH net-next v2 0/4] packet: add cBPF and eBPF fanout modes David Miller
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=55D0549C.5040104@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=ast@plumgrid$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=willemb@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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