From: Alexei Starovoitov <ast@fb.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 0/2] bpf: parallel verification
Date: Tue, 23 Apr 2019 00:06:55 +0000 [thread overview]
Message-ID: <28461404-f098-ef19-70c1-9ed1ac4ce449@fb.com> (raw)
In-Reply-To: <a58562b8-4501-d976-29b7-aec15475afe5@iogearbox.net>
On 4/22/19 4:58 PM, Daniel Borkmann wrote:
> On 04/19/2019 04:44 PM, Alexei Starovoitov wrote:
>> Allow the bpf verifier to run in parallel for root.
>>
>> Alexei Starovoitov (2):
>> bpf: remove global variables
>> bpf: drop bpf_verifier_lock
>>
>> include/linux/bpf_verifier.h | 5 +++++
>> kernel/bpf/verifier.c | 33 ++++++++++++++++++---------------
>> 2 files changed, 23 insertions(+), 15 deletions(-)
>>
>
> Too bad we still need to keep it around for unpriv. Anyway, applied, thanks!
I'm planing to add memcg accounting and teach oom_badness
about the memory used during verification. Then we can drop
the mutex for unpriv as well.
prev parent reply other threads:[~2019-04-23 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 14:44 [PATCH bpf-next 0/2] bpf: parallel verification Alexei Starovoitov
2019-04-19 14:44 ` [PATCH bpf-next 1/2] bpf: remove global variables Alexei Starovoitov
2019-04-19 14:44 ` [PATCH bpf-next 2/2] bpf: drop bpf_verifier_lock Alexei Starovoitov
2019-04-19 19:34 ` [PATCH bpf-next 0/2] bpf: parallel verification Andrii Nakryiko
2019-04-22 23:58 ` Daniel Borkmann
2019-04-23 0:06 ` 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=28461404-f098-ef19-70c1-9ed1ac4ce449@fb.com \
--to=ast@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.