From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Stanislav Fomichev <sdf@google.com>
Cc: Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next v9 0/3] bpf: misc performance improvements for cgroup hooks
Date: Wed, 20 Jan 2021 14:32:59 -0800 [thread overview]
Message-ID: <CAADnVQK0b6n_f4PM5eOT9oZxE6RmtaQneCZAHOJe5uosxO9S_Q@mail.gmail.com> (raw)
In-Reply-To: <20210115163501.805133-1-sdf@google.com>
On Fri, Jan 15, 2021 at 8:35 AM Stanislav Fomichev <sdf@google.com> wrote:
>
> First patch adds custom getsockopt for TCP_ZEROCOPY_RECEIVE
> to remove kmalloc and lock_sock overhead from the dat path.
>
> Second patch removes kzalloc/kfree from getsockopt for the common cases.
>
> Third patch switches cgroup_bpf_enabled to be per-attach to
> to add only overhead for the cgroup attach types used on the system.
>
> No visible user-side changes.
>
> v9:
> - include linux/tcp.h instead of netinet/tcp.h in sockopt_sk.c
> - note that v9 depends on the commit 4be34f3d0731 ("bpf: Don't leak
> memory in bpf getsockopt when optlen == 0") from bpf tree
I've rebased bpf-next to include that fix from bpf and applied this set.
Thanks!
prev parent reply other threads:[~2021-01-21 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 16:34 [PATCH bpf-next v9 0/3] bpf: misc performance improvements for cgroup hooks Stanislav Fomichev
2021-01-15 16:34 ` [PATCH bpf-next v9 1/3] bpf: remove extra lock_sock for TCP_ZEROCOPY_RECEIVE Stanislav Fomichev
2021-01-15 16:35 ` [PATCH bpf-next v9 2/3] bpf: try to avoid kzalloc in cgroup/{s,g}etsockopt Stanislav Fomichev
2021-01-15 16:35 ` [PATCH bpf-next v9 3/3] bpf: split cgroup_bpf_enabled per attach type Stanislav Fomichev
2021-01-20 22:32 ` Alexei Starovoitov [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=CAADnVQK0b6n_f4PM5eOT9oZxE6RmtaQneCZAHOJe5uosxO9S_Q@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.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).