[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL+tcoCA3MAGgVBod+FSUXxThPYJ3+XfQR9k+dWk0YLd3fAnkg@mail.gmail.com>
Date: Wed, 9 Oct 2024 16:11:15 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Kuniyuki Iwashima <kuniyu@...zon.com>
Cc: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
daniel@...earbox.net, davem@...emloft.net, dsahern@...nel.org,
eddyz87@...il.com, edumazet@...gle.com, haoluo@...gle.com,
john.fastabend@...il.com, jolsa@...nel.org, kernelxing@...cent.com,
kpsingh@...nel.org, kuba@...nel.org, martin.lau@...ux.dev,
netdev@...r.kernel.org, pabeni@...hat.com, sdf@...ichev.me, song@...nel.org,
willemb@...gle.com, willemdebruijn.kernel@...il.com, yonghong.song@...ux.dev
Subject: Re: [PATCH net-next 1/9] net-timestamp: add bpf infrastructure to
allow exposing more information later
On Wed, Oct 9, 2024 at 8:59 AM Kuniyuki Iwashima <kuniyu@...zon.com> wrote:
>
> From: Jason Xing <kerneljasonxing@...il.com>
> Date: Tue, 8 Oct 2024 17:51:01 +0800
> > From: Jason Xing <kernelxing@...cent.com>
> >
> > Implement basic codes so that we later can easily add each tx points.
> > Introducing BPF_SOCK_OPS_ALL_CB_FLAGS used as a test statement can help use
> > control whether to output or not.
> >
> > Signed-off-by: Jason Xing <kernelxing@...cent.com>
> > ---
> > include/uapi/linux/bpf.h | 5 ++++-
> > net/core/skbuff.c | 18 ++++++++++++++++++
> > tools/include/uapi/linux/bpf.h | 5 ++++-
> > 3 files changed, 26 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> > index c6cd7c7aeeee..157e139ed6fc 100644
> > --- a/include/uapi/linux/bpf.h
> > +++ b/include/uapi/linux/bpf.h
> > @@ -6900,8 +6900,11 @@ enum {
> > * options first before the BPF program does.
> > */
> > BPF_SOCK_OPS_WRITE_HDR_OPT_CB_FLAG = (1<<6),
> > + /* Call bpf when the kernel is generating tx timestamps.
> > + */
> > + BPF_SOCK_OPS_TX_TIMESTAMPING_OPT_CB_FLAG = (1<<7),
> > /* Mask of all currently supported cb flags */
> > - BPF_SOCK_OPS_ALL_CB_FLAGS = 0x7F,
> > + BPF_SOCK_OPS_ALL_CB_FLAGS = 0xFF,
>
> I remember this change makes two selftests fail and needs diff
> in this link.
> https://lore.kernel.org/bpf/20231016161134.25365-1-kuniyu@amazon.com/
Thanks for pointing out this. I will dig into this :)
>
> Also, adding a bpf selftest or extending some for this series
> would be nice.
Sure, I would like to add a selftest after we all reach a consensus on
how to implement it in the right way.
Thanks,
Jason
Powered by blists - more mailing lists