From: Tushar Dave <tushar.n.dave@oracle.com>
To: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
jakub.kicinski@netronome.com, quentin.monnet@netronome.com,
jiong.wang@netronome.com, guro@fb.com,
sandipan@linux.vnet.ibm.com, john.fastabend@gmail.com,
kafai@fb.com, rdna@fb.com, brakmo@fb.com, netdev@vger.kernel.org,
acme@redhat.com, sowmini.varadhan@oracle.com
Subject: Re: [RFC v2 PATCH 0/4] eBPF and struct scatterlist
Date: Mon, 25 Jun 2018 17:14:12 -0700 [thread overview]
Message-ID: <0d049228-cf44-f37e-213a-03db5da38958@oracle.com> (raw)
In-Reply-To: <1529431217-5264-1-git-send-email-tushar.n.dave@oracle.com>
On 06/19/2018 11:00 AM, Tushar Dave wrote:
> This follows up on https://patchwork.ozlabs.org/cover/927050/
> where the review feedback was to use bpf_skb_load_bytes() to deal with
> linear and non-linear skbs. While that feedback is valid and correct,
> the motivation for this work is to allow eBPF based firewalling for
> kernel modules that do not always get their packet as an sk_buff from
> their downlink drivers. One such instance of this use-case is RDS, which
> can be run both over IB (driver RDMA's a scatterlist to the RDS module)
> or over TCP (TCP passes an sk_buff to the RDS module)
>
> This RFC (call it v2) uses exiting socket filter infrastructure and
> extend it with new eBPF program type that deals with struct scatterlist.
> For RDS, the integrated approach treats the scatterlist as the common
> denominator, and allows the application to write a filter for processing
> a scatterlist.
>
>
> Details:
> Patch 1 adds new eBPF prog type BPF_PROG_TYPE_SOCKET_SG_FILTER which
> uses the existing socket filter infrastructure for bpf program attach
> and load. eBPF program of type BPF_PROG_TYPE_SOCKET_SG_FILTER receives
> struct scatterlist as bpf context contrast to
> BPF_PROG_TYPE_SOCKET_FILTER which deals with struct skb. This new eBPF
> program type allow socket filter to run on packet data that is in form
> form of struct scatterlist.
>
> Patch 2 adds functionality to run BPF_PROG_TYPE_SOCKET_SG_FILTER socket
> filter program. A bpf helpers bpf_sg_next() is also added so users can
> retrieve sg elements from scatterlist.
>
> Patch 3 adds socket filter eBPF sample program that uses patch 1 and
> patch 2. The sample program opens an rds socket, attach ebpf program
> (socksg i.e. BPF_PROG_TYPE_SOCKET_SG_FILTER) to rds socket and uses
> bpf_sg_next helper to look into sg. For a test, current ebpf program
> only prints first few bytes from each elements of sg list.
>
> Finally, patch 4 allows rds_recv_incoming to invoke socket filter
> program which deals with scatterlist.
It would be really helpful to have your thoughts/comments on my
direction. I am planning to put together some complex example for
filtering RDS traffic using eBPF, and so it would be good to have
feedback before I go too far ahead.
Thanks.
-Tushar
>
> Thanks.
>
> -Tushar
>
> Tushar Dave (4):
> eBPF: Add new eBPF prog type BPF_PROG_TYPE_SOCKET_SG_FILTER
> ebpf: Add sg_filter_run and sg helper
> ebpf: Add sample ebpf program for SOCKET_SG_FILTER
> rds: invoke socket sg filter attached to rds socket
>
> include/linux/bpf_types.h | 1 +
> include/linux/filter.h | 10 +
> include/uapi/linux/bpf.h | 17 +-
> kernel/bpf/syscall.c | 1 +
> kernel/bpf/verifier.c | 1 +
> net/core/filter.c | 149 ++++++++++++-
> net/rds/ib.c | 1 +
> net/rds/ib.h | 1 +
> net/rds/ib_recv.c | 12 ++
> net/rds/rds.h | 2 +
> net/rds/recv.c | 16 ++
> net/rds/tcp.c | 2 +
> net/rds/tcp.h | 2 +
> net/rds/tcp_recv.c | 38 ++++
> samples/bpf/Makefile | 3 +
> samples/bpf/bpf_load.c | 11 +-
> samples/bpf/rds_filter_kern.c | 78 +++++++
> samples/bpf/rds_filter_user.c | 339 ++++++++++++++++++++++++++++++
> tools/bpf/bpftool/prog.c | 1 +
> tools/include/uapi/linux/bpf.h | 17 +-
> tools/lib/bpf/libbpf.c | 3 +
> tools/lib/bpf/libbpf.h | 2 +
> tools/testing/selftests/bpf/bpf_helpers.h | 3 +
> 23 files changed, 703 insertions(+), 7 deletions(-)
> create mode 100644 samples/bpf/rds_filter_kern.c
> create mode 100644 samples/bpf/rds_filter_user.c
>
prev parent reply other threads:[~2018-06-26 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 18:00 [RFC v2 PATCH 0/4] eBPF and struct scatterlist Tushar Dave
2018-06-19 18:00 ` [RFC v2 PATCH 1/4] eBPF: Add new eBPF prog type BPF_PROG_TYPE_SOCKET_SG_FILTER Tushar Dave
2018-06-29 7:25 ` Daniel Borkmann
2018-06-29 8:48 ` Daniel Borkmann
2018-06-30 0:20 ` Tushar Dave
2018-06-29 8:27 ` Daniel Borkmann
2018-06-30 0:46 ` Tushar Dave
2018-06-19 18:00 ` [RFC v2 PATCH 2/4] ebpf: Add sg_filter_run and sg helper Tushar Dave
2018-06-29 8:18 ` Daniel Borkmann
2018-06-30 0:24 ` Tushar Dave
2018-06-29 8:32 ` Daniel Borkmann
2018-06-30 0:27 ` Tushar Dave
2018-06-19 18:00 ` [RFC v2 PATCH 3/4] ebpf: Add sample ebpf program for SOCKET_SG_FILTER Tushar Dave
2018-06-19 18:00 ` [RFC v2 PATCH 4/4] rds: invoke socket sg filter attached to rds socket Tushar Dave
2018-06-26 0:14 ` Tushar Dave [this message]
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=0d049228-cf44-f37e-213a-03db5da38958@oracle.com \
--to=tushar.n.dave@oracle.com \
--cc=acme@redhat.com \
--cc=ast@kernel.org \
--cc=brakmo@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=guro@fb.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiong.wang@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.com \
--cc=rdna@fb.com \
--cc=sandipan@linux.vnet.ibm.com \
--cc=sowmini.varadhan@oracle.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;
as well as URLs for NNTP newsgroup(s).