[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250204175052.6abc3d2d@kernel.org>
Date: Tue, 4 Feb 2025 17:50:52 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jason Xing <kerneljasonxing@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, 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, horms@...nel.org,
bpf@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next v8 05/12] net-timestamp: prepare for isolating
two modes of SO_TIMESTAMPING
On Wed, 5 Feb 2025 02:30:17 +0800 Jason Xing wrote:
> void __skb_tstamp_tx(struct sk_buff *orig_skb,
> const struct sk_buff *ack_skb,
> struct skb_shared_hwtstamps *hwtstamps,
> - struct sock *sk, int tstype)
> + struct sock *sk, bool sw, int tstype)
> {
> struct sk_buff *skb;
> bool tsonly, opt_stats = false;
> @@ -5551,6 +5576,9 @@ void __skb_tstamp_tx(struct sk_buff *orig_skb,
> if (!sk)
> return;
>
> + if (!skb_enable_app_tstamp(orig_skb, tstype, sw))
maybe keep the order of @tstype vs @sw consistent?
Powered by blists - more mailing lists