From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <ast@fb.com>,
bpf@vger.kernel.org, Networking <netdev@vger.kernel.org>,
joe@wand.net.nz, john.fastabend@gmail.com, tgraf@suug.ch,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
lmb@cloudflare.com
Subject: Re: [PATCH bpf-next v2 1/7] bpf: implement lookup-free direct value access
Date: Fri, 1 Mar 2019 10:50:54 -0800 [thread overview]
Message-ID: <20190301105054.727f8e28@cakuba.netronome.com> (raw)
In-Reply-To: <93040e2a-cf74-0dfe-276f-0a91598011c5@iogearbox.net>
On Fri, 1 Mar 2019 10:49:46 +0100, Daniel Borkmann wrote:
> Overall, BPF_PSEUDO_MAP_VALUE felt slightly more suitable to me.
FWIW +1 I think different type is way cleaner here.
next prev parent reply other threads:[~2019-03-01 18:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 23:18 [PATCH bpf-next v2 0/7] BPF support for global data Daniel Borkmann
2019-02-28 23:18 ` [PATCH bpf-next v2 1/7] bpf: implement lookup-free direct value access Daniel Borkmann
2019-03-01 3:33 ` Jann Horn
2019-03-01 3:58 ` kbuild test robot
2019-03-01 5:46 ` Andrii Nakryiko
2019-03-01 9:49 ` Daniel Borkmann
2019-03-01 18:50 ` Jakub Kicinski [this message]
2019-03-01 19:35 ` Andrii Nakryiko
2019-03-01 20:08 ` Jakub Kicinski
2019-03-01 17:18 ` Yonghong Song
2019-03-01 19:51 ` Daniel Borkmann
2019-03-01 23:02 ` Yonghong Song
2019-03-04 6:03 ` Andrii Nakryiko
2019-03-04 15:59 ` Daniel Borkmann
2019-03-04 17:32 ` Andrii Nakryiko
2019-02-28 23:18 ` [PATCH bpf-next v2 2/7] bpf: add program side {rd,wr}only support Daniel Borkmann
2019-03-01 3:51 ` Jakub Kicinski
2019-03-01 9:01 ` Daniel Borkmann
2019-02-28 23:18 ` [PATCH bpf-next v2 3/7] bpf, obj: allow . char as part of the name Daniel Borkmann
2019-03-01 5:52 ` Andrii Nakryiko
2019-03-01 9:04 ` Daniel Borkmann
2019-02-28 23:18 ` [PATCH bpf-next v2 4/7] bpf, libbpf: refactor relocation handling Daniel Borkmann
2019-02-28 23:18 ` [PATCH bpf-next v2 5/7] bpf, libbpf: support global data/bss/rodata sections Daniel Borkmann
2019-02-28 23:41 ` Stanislav Fomichev
2019-03-01 0:19 ` Daniel Borkmann
2019-03-02 0:23 ` Yonghong Song
2019-03-02 0:27 ` Daniel Borkmann
2019-03-01 6:53 ` Andrii Nakryiko
2019-03-01 10:46 ` Daniel Borkmann
2019-03-01 18:10 ` Stanislav Fomichev
2019-03-01 18:46 ` Andrii Nakryiko
2019-03-01 18:11 ` Yonghong Song
2019-03-01 18:48 ` Andrii Nakryiko
2019-03-01 18:58 ` Yonghong Song
2019-03-01 19:10 ` Andrii Nakryiko
2019-03-01 19:19 ` Yonghong Song
2019-03-01 20:06 ` Daniel Borkmann
2019-03-01 20:25 ` Yonghong Song
2019-03-01 20:33 ` Daniel Borkmann
2019-03-05 2:28 ` static bpf vars. Was: " Alexei Starovoitov
2019-03-05 9:31 ` Daniel Borkmann
2019-03-01 19:56 ` Daniel Borkmann
2019-02-28 23:18 ` [PATCH bpf-next v2 6/7] bpf, selftest: test " Daniel Borkmann
2019-03-01 19:13 ` Andrii Nakryiko
2019-03-01 20:02 ` Daniel Borkmann
2019-03-04 8:48 ` [LKP] [bpf, selftest] 4beb1a5f45: kernel_selftests.bpf.make_fail kernel test robot
2019-03-04 8:48 ` kernel test robot
2019-02-28 23:18 ` [PATCH bpf-next v2 7/7] bpf, selftest: test {rd,wr}only flags and direct value access Daniel Borkmann
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=20190301105054.727f8e28@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=joe@wand.net.nz \
--cc=john.fastabend@gmail.com \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=yhs@fb.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 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.