[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQLbC-KVNRPgbJP3rokgLELam5ao1-Fnpej8d-9JaHMJPA@mail.gmail.com>
Date: Fri, 10 Jun 2022 14:52:52 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Toke Høiland-Jørgensen <toke@...hat.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Kumar Kartikeya Dwivedi <memxor@...il.com>,
Joanne Koong <joannelkoong@...il.com>,
bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Vlad Buslov <vladbu@...dia.com>,
Cong Wang <xiyou.wangcong@...il.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH bpf-next v2 0/7] Add bpf_link based TC-BPF API
On Fri, Jun 10, 2022 at 1:41 PM Toke Høiland-Jørgensen <toke@...hat.com> wrote:
>
> >> Except we'd want to also support multiple programs on different
> >> priorities? I don't think requiring a libxdp-like dispatcher to achieve
> >> this is a good idea if we can just have it be part of the API from the
> >> get-go...
> >
> > Yes, it will be multi-prog to avoid a situation where dispatcher is needed.
>
> Awesome! :)
Let's keep it simple to start.
Priorities or anything fancy can be added later if really necessary.
Otherwise, I'm afraid, we will go into endless bikeshedding
or the best priority scheme.
A link list of bpf progs like cls_bpf with the same semantics as
cls_bpf_classify.
With prog->exts_integrated always true and no classid, since this
concept doesn't apply.
Powered by blists - more mailing lists