From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"Yonghong Song" <yhs@fb.com>, bpf <bpf@vger.kernel.org>
Subject: Re: Latest libbpf fails to load programs compiled with old LLVM
Date: Mon, 7 Dec 2020 11:59:47 -0700 [thread overview]
Message-ID: <9d91a663-abd3-603d-de5e-26c572eeac05@gmail.com> (raw)
In-Reply-To: <CAADnVQKdQdxAouvFGAWr+xT73=JZGkaKdTObsDW0GAnjcDzx9g@mail.gmail.com>
On 12/7/20 11:14 AM, Alexei Starovoitov wrote:
> On Mon, Dec 7, 2020 at 10:02 AM David Ahern <dsahern@gmail.com> wrote:
>>
>> On 12/7/20 9:20 AM, Alexei Starovoitov wrote:
>>> The user space library is not a kernel.
>>> The library will change its interface. It will remove functions, features, etc.
>>> That's what .map is for.
>>
>> So any user/package wanting to leverage libbpf can not expect stability
>> or consistency with its APIs?
>
> If you're talking about iproute2 and your own convoluted definition of
your record player seems to be stuck. Could you give it a little bump so
it can move on to the next track? Thanks. I do work on other things
besides iproute2.
> stability and consistency then certainly not.
>
Your statement has huge impacts on what users can expect from a library
and is inconsistent with other libraries I have used. Hence, my request
for clarification on your comment about 'changing interfaces, removing
functions and features.'
next prev parent reply other threads:[~2020-12-07 19:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 17:55 Latest libbpf fails to load programs compiled with old LLVM Toke Høiland-Jørgensen
2020-12-04 1:42 ` Yonghong Song
2020-12-04 9:34 ` Toke Høiland-Jørgensen
2020-12-04 17:54 ` Yonghong Song
2020-12-04 19:23 ` Andrii Nakryiko
2020-12-07 10:59 ` Toke Høiland-Jørgensen
2020-12-07 15:55 ` Alexei Starovoitov
2020-12-07 16:15 ` Toke Høiland-Jørgensen
2020-12-07 16:20 ` Alexei Starovoitov
2020-12-07 16:51 ` Toke Høiland-Jørgensen
2020-12-07 17:16 ` Alexei Starovoitov
2020-12-07 22:18 ` Toke Høiland-Jørgensen
2020-12-08 1:20 ` Alexei Starovoitov
2020-12-07 18:02 ` David Ahern
2020-12-07 18:14 ` Alexei Starovoitov
2020-12-07 18:59 ` David Ahern [this message]
2020-12-08 2:47 ` Andrii Nakryiko
2020-12-08 13:41 ` Toke Høiland-Jørgensen
2020-12-08 18:39 ` Andrii Nakryiko
2020-12-08 22:38 ` Toke Høiland-Jørgensen
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=9d91a663-abd3-603d-de5e-26c572eeac05@gmail.com \
--to=dsahern@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=toke@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox