[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67b497e197e5c_10d6a329432@willemb.c.googlers.com.notmuch>
Date: Tue, 18 Feb 2025 09:23:29 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Jason Xing <kerneljasonxing@...il.com>,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
dsahern@...nel.org,
willemdebruijn.kernel@...il.com,
willemb@...gle.com,
ast@...nel.org,
daniel@...earbox.net,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
john.fastabend@...il.com,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org,
shuah@...nel.org,
ykolal@...com
Cc: bpf@...r.kernel.org,
netdev@...r.kernel.org,
Jason Xing <kerneljasonxing@...il.com>
Subject: Re: [PATCH bpf-next v12 06/12] bpf: add BPF_SOCK_OPS_TS_SCHED_OPT_CB
callback
Jason Xing wrote:
> Support SCM_TSTAMP_SCHED case for bpf timestamping.
>
> Add a new sock_ops callback, BPF_SOCK_OPS_TS_SCHED_OPT_CB. This
> callback will occur at the same timestamping point as the user
> space's SCM_TSTAMP_SCHED. The BPF program can use it to get the
> same SCM_TSTAMP_SCHED timestamp without modifying the user-space
> application.
>
> A new SKBTX_BPF flag is added to mark skb_shinfo(skb)->tx_flags,
> ensuring that the new BPF timestamping and the current user
> space's SO_TIMESTAMPING do not interfere with each other.
>
> Signed-off-by: Jason Xing <kerneljasonxing@...il.com>
Reviewed-by: Willem de Bruijn <willemb@...gle.com>
Powered by blists - more mailing lists