From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: pull-request: bpf-next 2022-09-05
Date: Mon, 19 Sep 2022 09:26:18 -0700 [thread overview]
Message-ID: <20220919092618.146f47a3@kernel.org> (raw)
In-Reply-To: <20220905161136.9150-1-daniel@iogearbox.net>
On Mon, 5 Sep 2022 18:11:36 +0200 Daniel Borkmann wrote:
> 1) Add any-context BPF specific memory allocator which is useful in particular for BPF
> tracing with bonus of performance equal to full prealloc, from Alexei Starovoitov.
The MM folks basically acquiesced that this is BPF-specific
and does not concern them? Would had been great to squeeze
an ack out of someone.
prev parent reply other threads:[~2022-09-19 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 16:11 pull-request: bpf-next 2022-09-05 Daniel Borkmann
2022-09-06 22:10 ` patchwork-bot+netdevbpf
2022-09-19 16:26 ` Jakub Kicinski [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=20220919092618.146f47a3@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).