From: Ferenc Fejes <fejes@inf.elte.hu>
To: netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
Martin KaFai Lau <kafai@fb.com>,
"David S . Miller" <davem@davemloft.net>,
Ferenc Fejes <fejes@inf.elte.hu>
Subject: [PATCH v2 net-next 0/3] Extending bpf_setsockopt with SO_BINDTODEVICE sockopt
Date: Sat, 30 May 2020 23:08:59 +0200 [thread overview]
Message-ID: <cover.1590871065.git.fejes@inf.elte.hu> (raw)
This option makes it possible to programatically bind sockets
to netdevices. With the help of this option sockets
of VRF unaware applications could be distributed between
multiple VRFs with an eBPF program. This lets the applications
benefit from multiple possible routes.
v2:
- splitting up the patch to three parts
- lock_sk parameter for optional locking in sock_bindtoindex - Stanislav Fomichev
- testing the SO_BINDTODEVICE option - Andrii Nakryiko
Ferenc Fejes (3):
net: Make locking in sock_bindtoindex optional
bpf: Allow SO_BINDTODEVICE opt in bpf_setsockopt
selftests/bpf: Add test for SO_BINDTODEVICE opt of bpf_setsockopt
include/net/sock.h | 2 +-
net/core/filter.c | 27 ++++++++++++++-
net/core/sock.c | 10 +++---
net/ipv4/udp_tunnel.c | 2 +-
net/ipv6/ip6_udp_tunnel.c | 2 +-
.../selftests/bpf/progs/connect4_prog.c | 33 +++++++++++++++++++
6 files changed, 68 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2020-05-30 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 21:08 Ferenc Fejes [this message]
2020-05-30 21:09 ` [PATCH v2 net-next 1/3] net: Make locking in sock_bindtoindex optional Ferenc Fejes
2020-05-30 21:09 ` [PATCH v2 net-next 2/3] bpf: Allow SO_BINDTODEVICE opt in bpf_setsockopt Ferenc Fejes
2020-05-30 21:09 ` [PATCH v2 net-next 3/3] selftests/bpf: Add test for SO_BINDTODEVICE opt of bpf_setsockopt Ferenc Fejes
2020-06-01 22:02 ` [PATCH v2 net-next 0/3] Extending bpf_setsockopt with SO_BINDTODEVICE sockopt Alexei Starovoitov
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=cover.1590871065.git.fejes@inf.elte.hu \
--to=fejes@inf.elte.hu \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.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).