From: Martin Lau <kafai@fb.com>
To: Stanislav Fomichev <sdf@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next v5 0/8] bpf: getsockopt and setsockopt hooks
Date: Mon, 10 Jun 2019 21:38:55 +0000 [thread overview]
Message-ID: <20190610213853.vx4dtpspzgvsspez@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20190610210830.105694-1-sdf@google.com>
On Mon, Jun 10, 2019 at 02:08:22PM -0700, Stanislav Fomichev wrote:
> This series implements two new per-cgroup hooks: getsockopt and
> setsockopt along with a new sockopt program type. The idea is pretty
> similar to recently introduced cgroup sysctl hooks, but
> implementation is simpler (no need to convert to/from strings).
>
> What this can be applied to:
> * move business logic of what tos/priority/etc can be set by
> containers (either pass or reject)
> * handle existing options (or introduce new ones) differently by
> propagating some information in cgroup/socket local storage
>
> Compared to a simple syscall/{g,s}etsockopt tracepoint, those
> hooks are context aware. Meaning, they can access underlying socket
> and use cgroup and socket local storage.
Acked-by: Martin KaFai Lau <kafai@fb.com>
prev parent reply other threads:[~2019-06-10 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:08 [PATCH bpf-next v5 0/8] bpf: getsockopt and setsockopt hooks Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 1/8] bpf: implement " Stanislav Fomichev
2019-06-13 20:16 ` Alexei Starovoitov
2019-06-13 21:20 ` Stanislav Fomichev
2019-06-13 21:50 ` Andrii Nakryiko
2019-06-13 21:54 ` Stanislav Fomichev
2019-06-14 16:32 ` Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 2/8] bpf: sync bpf.h to tools/ Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 3/8] libbpf: support sockopt hooks Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 4/8] selftests/bpf: test sockopt section name Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 5/8] selftests/bpf: add sockopt test Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 6/8] selftests/bpf: add sockopt test that exercises sk helpers Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 7/8] bpf: add sockopt documentation Stanislav Fomichev
2019-06-10 21:08 ` [PATCH bpf-next v5 8/8] bpftool: support cgroup sockopt Stanislav Fomichev
2019-06-10 21:38 ` Martin Lau [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=20190610213853.vx4dtpspzgvsspez@kafai-mbp.dhcp.thefacebook.com \
--to=kafai@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--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).