[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fc6a4f7ea0308626cfd06d95564486d187b16e0.camel@redhat.com>
Date: Thu, 29 Feb 2024 10:30:39 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Abhishek Chauhan <quic_abchauha@...cinc.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Andrew Halaney <ahalaney@...hat.com>, Willem de Bruijn
<willemdebruijn.kernel@...il.com>, Martin KaFai Lau
<martin.lau@...nel.org>, Martin KaFai Lau <martin.lau@...ux.dev>
Cc: kernel@...cinc.com
Subject: Re: [PATCH net-next v2] net: Modify mono_delivery_time with
clockid_delivery_time
On Tue, 2024-02-27 at 17:12 -0800, Abhishek Chauhan wrote:
> Bridge driver today has no support to forward the userspace timestamp
> packets and ends up resetting the timestamp. ETF qdisc checks the
> packet coming from userspace and encounters to be 0 thereby dropping
> time sensitive packets. These changes will allow userspace timestamps
> packets to be forwarded from the bridge to NIC drivers.
>
> Existing functionality of mono_delivery_time is not altered here
> instead just extended with userspace tstamp support for bridge
> forwarding path.
>
> Signed-off-by: Abhishek Chauhan <quic_abchauha@...cinc.com>
Since this is touching a quite sensitive code path, I think v3 would
deserve some paired self-tests.
Thanks!
Paolo
Powered by blists - more mailing lists