From: Jiri Benc <jbenc@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
daniel@iogearbox.net, ast@fb.com, andrii@kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org, brouer@redhat.com,
haliu@redhat.com, dsahern@gmail.com
Subject: Re: [PATCH bpf-next] libbpf: Add libbpf_version() function to get library version at runtime
Date: Thu, 19 Nov 2020 09:56:36 +0100 [thread overview]
Message-ID: <20201119095636.67c5b7ec@redhat.com> (raw)
In-Reply-To: <20201118174325.zjomd2gvybof6awa@ast-mbp>
On Wed, 18 Nov 2020 09:43:25 -0800, Alexei Starovoitov wrote:
> Just like the kernel doesn't add features for out-of-tree modules
> libbpf doesn't add features for projects where libbpf is optional.
A more fitting comparison would be the kernel refusing to add a new
uAPI call because some application refuses to bundle the kernel.
A libbpf equivalent of a kernel module would be some kind of libbpf
plugin (which does not exist), asking for an internal libbpf API to be
added.
Alexei, could you please start cooperating with others and actually
listening to others' needs? I know you started eBPF but you're not the
only user anymore and as much convinced you may be about your view,
people have reasons for what they're doing. It would help greatly if
you could listen to these reasons.
Jiri
next prev parent reply other threads:[~2020-11-19 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 17:07 [PATCH bpf-next] libbpf: Add libbpf_version() function to get library version at runtime Toke Høiland-Jørgensen
2020-11-18 17:43 ` Alexei Starovoitov
2020-11-18 18:01 ` Toke Høiland-Jørgensen
2020-11-19 8:56 ` Jiri Benc [this message]
2020-11-18 21:16 ` David Ahern
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=20201119095636.67c5b7ec@redhat.com \
--to=jbenc@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=haliu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=toke@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).