From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: "Toke Høiland-Jørgensen" <toke@kernel.org>,
bpf <bpf@vger.kernel.org>,
"Network Development" <netdev@vger.kernel.org>,
"Martin KaFai Lau" <martin.lau@kernel.org>,
"Nikolay Aleksandrov" <razor@blackwall.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>
Subject: Re: [PATCH bpf-next 1/8] meta, bpf: Add bpf programmable meta device
Date: Fri, 29 Sep 2023 12:25:17 -0700 [thread overview]
Message-ID: <CAADnVQK82PRjGnw+wht4ZpxK3s3St2qWRoO6bJbuY3cARXXPxQ@mail.gmail.com> (raw)
In-Reply-To: <11c6240c-ab6b-fba3-d84a-824b3fa36ac9@iogearbox.net>
On Thu, Sep 28, 2023 at 2:14 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
>
> > I think we should just name the driver 'bpfnet'; it's not pretty, but
> > it's obvious and descriptive. Optionally we could teach 'ip' to
> > understand just 'bpf' as the device type, so you could go 'ip link add
> > type bpf' and get one of these.
>
> I'll think about it, the bpfnet sounds terrible as you also noticed. I
> definitely don't like that. Perhaps meta_net as suggested by Andrii in
> the other thread could be a compromise. Need to sleep over it, my pref
> was actually to keep it shorter.
I don't like the meta name either standalone or as meta_net.
Maybe "hollow" or "void" netdevice?
Since this netdev doesn't have a substance when bpf prog is not attached.
It's empty == dummy == hollow == void netdevice.
next prev parent reply other threads:[~2023-09-29 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 5:59 [PATCH bpf-next 0/8] Add bpf programmable device Daniel Borkmann
2023-09-26 5:59 ` [PATCH bpf-next 1/8] meta, bpf: Add bpf programmable meta device Daniel Borkmann
2023-09-26 21:26 ` Stanislav Fomichev
2023-09-28 9:16 ` Toke Høiland-Jørgensen
2023-09-28 12:01 ` Willem de Bruijn
2023-09-28 21:14 ` Daniel Borkmann
2023-09-29 19:25 ` Alexei Starovoitov [this message]
2023-10-13 11:26 ` Florian Kauer
2023-09-26 5:59 ` [PATCH bpf-next 2/8] meta, bpf: Add bpf link support for " Daniel Borkmann
2023-09-28 0:12 ` Andrii Nakryiko
2023-09-26 5:59 ` [PATCH bpf-next 3/8] tools: Sync if_link uapi header Daniel Borkmann
2023-09-26 5:59 ` [PATCH bpf-next 4/8] libbpf: Add link-based API for meta Daniel Borkmann
2023-09-26 11:19 ` Quentin Monnet
2023-09-28 0:12 ` Andrii Nakryiko
2023-09-28 21:30 ` Daniel Borkmann
2023-09-26 5:59 ` [PATCH bpf-next 5/8] bpftool: Implement link show support " Daniel Borkmann
2023-09-26 11:19 ` Quentin Monnet
2023-09-26 5:59 ` [PATCH bpf-next 6/8] bpftool: Extend net dump with meta progs Daniel Borkmann
2023-09-26 11:19 ` Quentin Monnet
2023-09-26 5:59 ` [PATCH bpf-next 7/8] selftests/bpf: Add netlink helper library Daniel Borkmann
2023-09-26 21:35 ` Stanislav Fomichev
2023-09-26 5:59 ` [PATCH bpf-next 8/8] selftests/bpf: Add selftests for meta 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=CAADnVQK82PRjGnw+wht4ZpxK3s3St2qWRoO6bJbuY3cARXXPxQ@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=toke@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).