From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: daniel@iogearbox.net, jakub.kicinski@netronome.com,
brendan.d.gregg@gmail.com, john.fastabend@gmail.com,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next] bpf: document answers to common questions about BPF
Date: Wed, 01 Nov 2017 21:02:12 +0900 (KST) [thread overview]
Message-ID: <20171101.210212.1846332722129715994.davem@davemloft.net> (raw)
In-Reply-To: <20171031023956.1996684-1-ast@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Mon, 30 Oct 2017 19:39:56 -0700
> to address common misconceptions about what BPF is and what it's not
> add short BPF Q&A that clarifies core BPF design principles and
> answers some common questions.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: John Fastabend <john.fastabend@gmail.com>
> Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Looks great, applied, thanks!
prev parent reply other threads:[~2017-11-01 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 2:39 [PATCH net-next] bpf: document answers to common questions about BPF Alexei Starovoitov
2017-11-01 12:02 ` David Miller [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=20171101.210212.1846332722129715994.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--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 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).