[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMB2axO+==foKE3vBsyDAxbgZVz1S0iocAinr7bYWGye+z8yCQ@mail.gmail.com>
Date: Fri, 14 Mar 2025 09:43:20 +0800
From: Amery Hung <ameryhung@...il.com>
To: Toke Høiland-Jørgensen <toke@...hat.com>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org, daniel@...earbox.net,
andrii@...nel.org, alexei.starovoitov@...il.com, martin.lau@...nel.org,
kuba@...nel.org, edumazet@...gle.com, xiyou.wangcong@...il.com,
jhs@...atatu.com, sinquersw@...il.com, jiri@...nulli.us, stfomichev@...il.com,
ekarani.silvestre@....ufcg.edu.br, yangpeihao@...u.edu.cn,
yepeilin.cs@...il.com, kernel-team@...a.com
Subject: Re: [PATCH bpf-next v5 00/13] bpf qdisc
On Fri, Mar 14, 2025 at 3:52 AM Toke Høiland-Jørgensen <toke@...hat.com> wrote:
>
> Amery Hung <ameryhung@...il.com> writes:
>
> > Hi all,
> >
> > This patchset aims to support implementing qdisc using bpf struct_ops.
> > This version takes a step back and only implements the minimum support
> > for bpf qdisc. 1) support of adding skb to bpf_list and bpf_rbtree
> > directly and 2) classful qdisc are deferred to future patchsets. In
> > addition, we only allow attaching bpf qdisc to root or mq for now.
> > This is to prevent accidentally breaking exisiting classful qdiscs
> > that rely on data in a child qdisc. This limit may be lifted in the
> > future after careful inspection.
>
> Very cool to see this progress!
>
> Are you aware that the series has a mix of commit author email addresses
> (mixing your bytedance.com and gmail addresses)?
>
Yes. I have changed my affiliation so some recently added patches use
another email.
Thanks for reviewing!
Amery
> Otherwise, for the series:
>
> Acked-by: Toke Høiland-Jørgensen <toke@...hat.com>
>
Powered by blists - more mailing lists