On Fri, Aug 23, 2019 at 4:29 AM Toke Høiland-Jørgensen wrote:
>
> [ ... snip ...]
>
> > E.g., today's API is essentially three steps:
> >
> > 1. open and parse ELF: collect relos, programs, map definitions
> > 2. load: create maps from collected defs, do program/global data/CO-RE
> > relocs, load
On Fri, Aug 23, 2019 at 3:27 AM Jesper Dangaard Brouer
wrote:
>
> On Wed, 21 Aug 2019 13:30:09 -0700
> Andrii Nakryiko wrote:
>
> > On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> > wrote:
> > >
> > > iproute2 uses its own bpf loader to load eBPF programs, which has
> > > evolved separ
[ ... snip ...]
> E.g., today's API is essentially three steps:
>
> 1. open and parse ELF: collect relos, programs, map definitions
> 2. load: create maps from collected defs, do program/global data/CO-RE
> relocs, load and verify BPF programs
> 3. attach programs one by one.
>
> Between step 1 an
On Wed, 21 Aug 2019 13:30:09 -0700
Andrii Nakryiko wrote:
> On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> wrote:
> >
> > iproute2 uses its own bpf loader to load eBPF programs, which has
> > evolved separately from libbpf. Since we are now standardising on
> > libbpf, this becomes a
On Thu, Aug 22, 2019 at 1:33 AM Daniel Borkmann wrote:
>
> On 8/22/19 9:49 AM, Andrii Nakryiko wrote:
> > On Wed, Aug 21, 2019 at 2:07 PM Toke Høiland-Jørgensen
> > wrote:
> >> Andrii Nakryiko writes:
> >>> On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> >>> wrote:
>
> ipro
Toke Høiland-Jørgensen writes:
> Daniel Borkmann writes:
>
>> On 8/22/19 9:49 AM, Andrii Nakryiko wrote:
>>> On Wed, Aug 21, 2019 at 2:07 PM Toke Høiland-Jørgensen
>>> wrote:
Andrii Nakryiko writes:
> On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> wrote:
>>
>>
Daniel Borkmann writes:
> On 8/22/19 9:49 AM, Andrii Nakryiko wrote:
>> On Wed, Aug 21, 2019 at 2:07 PM Toke Høiland-Jørgensen
>> wrote:
>>> Andrii Nakryiko writes:
On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
wrote:
>
> iproute2 uses its own bpf loader to load eB
Andrii Nakryiko writes:
> On Wed, Aug 21, 2019 at 4:29 PM Toke Høiland-Jørgensen
> wrote:
>>
>> Alexei Starovoitov writes:
>>
>> > On Tue, Aug 20, 2019 at 01:47:01PM +0200, Toke Høiland-Jørgensen wrote:
>> >> iproute2 uses its own bpf loader to load eBPF programs, which has
>> >> evolved separ
On 8/22/19 9:49 AM, Andrii Nakryiko wrote:
On Wed, Aug 21, 2019 at 2:07 PM Toke Høiland-Jørgensen wrote:
Andrii Nakryiko writes:
On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen wrote:
iproute2 uses its own bpf loader to load eBPF programs, which has
evolved separately from libbpf. S
On Wed, Aug 21, 2019 at 4:29 PM Toke Høiland-Jørgensen wrote:
>
> Alexei Starovoitov writes:
>
> > On Tue, Aug 20, 2019 at 01:47:01PM +0200, Toke Høiland-Jørgensen wrote:
> >> iproute2 uses its own bpf loader to load eBPF programs, which has
> >> evolved separately from libbpf. Since we are now s
On Wed, Aug 21, 2019 at 2:07 PM Toke Høiland-Jørgensen wrote:
>
> Andrii Nakryiko writes:
>
> > On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> > wrote:
> >>
> >> iproute2 uses its own bpf loader to load eBPF programs, which has
> >> evolved separately from libbpf. Since we are now sta
Andrii Nakryiko writes:
> On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen
> wrote:
>>
>> iproute2 uses its own bpf loader to load eBPF programs, which has
>> evolved separately from libbpf. Since we are now standardising on
>> libbpf, this becomes a problem as iproute2 is slowly accumula
Alexei Starovoitov writes:
> On Tue, Aug 20, 2019 at 01:47:01PM +0200, Toke Høiland-Jørgensen wrote:
>> iproute2 uses its own bpf loader to load eBPF programs, which has
>> evolved separately from libbpf. Since we are now standardising on
>> libbpf, this becomes a problem as iproute2 is slowly ac
On Tue, Aug 20, 2019 at 4:47 AM Toke Høiland-Jørgensen wrote:
>
> iproute2 uses its own bpf loader to load eBPF programs, which has
> evolved separately from libbpf. Since we are now standardising on
> libbpf, this becomes a problem as iproute2 is slowly accumulating
> feature incompatibilities wi
On Tue, Aug 20, 2019 at 01:47:01PM +0200, Toke Høiland-Jørgensen wrote:
> iproute2 uses its own bpf loader to load eBPF programs, which has
> evolved separately from libbpf. Since we are now standardising on
> libbpf, this becomes a problem as iproute2 is slowly accumulating
> feature incompatibili
iproute2 uses its own bpf loader to load eBPF programs, which has
evolved separately from libbpf. Since we are now standardising on
libbpf, this becomes a problem as iproute2 is slowly accumulating
feature incompatibilities with libbpf-based loaders. In particular,
iproute2 has its own (expanded) v
16 matches
Mail list logo
