Re: [L4s-discuss] [EXTERNAL] Re: Interop·Labs Low Latency Low Loss Scalable Throughput (L4S) February 26-March 1, 2024 - Registration open

[rjmcmahon <[e-mail]>]

Hardware support for PTP is built in with a rpi 5.

root@rpi5-35:/usr/local/src/linux/drivers/net/ethernet/cadence# ethtool 
-T eth0
Time stamping parameters for eth0:
Capabilities:
	hardware-transmit
	software-transmit
	hardware-receive
	software-receive
	software-system-clock
	hardware-raw-clock
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
	off
	on
	onestep-sync
Hardware Receive Filter Modes:
	none
	all

I compiled the kernel from source

root@rpi5-35:/usr/local/src/linux/drivers/net/ethernet/cadence# uname -r
6.1.63-v8-16k+

PTP MAC code is in

root@rpi5-35:/usr/local/src/linux/drivers/net/ethernet/cadence# ls
built-in.a  Kconfig  macb.h  macb_main.c  macb_main.o  macb_pci.c  
macb_ptp.c  macb_ptp.o  Makefile  modules.order

The missing piece is L4S stack changes for these later kernel releases.

Bob

> Hi I just got a RPi5 ... can you elaborate on the hardware support?
> Are you saying it is built-in or that I need an external hardware
> module?
> 
> 
> -----Original Message-----
> From: L4s-discuss <[e-mail]> On Behalf Of rjmcmahon
> Sent: Thursday, January 25, 2024 7:03 PM
> To: Greg White <g.white=[e-mail]>
> Cc: rjmcmahon <rjmcmahon=[e-mail]>;
> [e-mail]; Renae Cox <[e-mail]>
> Subject: [EXTERNAL] Re: [L4s-discuss] Interop·Labs Low Latency Low
> Loss Scalable Throughput (L4S) February 26-March 1, 2024 -
> Registration open
> 
> Thanks. Forgot to mention the rpi4b ethernet doesn't support hardware
> PTP but the rpi 5 does (per something like ptp4l or linux ptp). The
> Rpi5 has a MAC from Cadence with this support.
> 
> Also, I haven't decoupled iperf 2 --bounceback read/write threads.
> I'll try to do that ahead of this in the event it's useful.
> 
> I haven't updated the tcp_info stats either. That's another todo item.
> EPBFs for CE marks might be useful too.
> 
> I try to avoid pcaps ;)
> 
> Bob
>> I think there is a good chance on GPS.  There are large windows with a
>> clear view of the sky in the interop lab.  I will verify.
>> 
>> We primarily use pcaps, capturing traffic at both ends of the link in
>> order to calculate and plot per-packet one way latency, ECN state
>> changes, QP sanctioning events, packet drops precisely, so we've not
>> needed clock synchronization, and this works for all application
>> traffic types.
>> 
>> -Greg
>> 
>> 
>> 
>> On 1/25/24, 2:39 PM, "rjmcmahon"
>> <rjmcmahon=[e-mail]
>> <mailto:[e-mail]>> wrote:
>> 
>> 
>> Any chance of having a GPS signal in the space? Or a PTP grandmaster
>> and a low latency and low jitter switch for PTP multicast? This will
>> allow for clock sync and enable iperf 2 one way delay (OWD) metrics
>> which can provide insights as to what's going on.
>> 
>> 
>> Also, I'm now using rasperry pi 5's with GPS for iperf 2 development
>> because they are inexpensive, have hardware PTP, have a realtime clock
>> (RTC), have GPIO pulse per second, and outperform rpi 4's per a more
>> than doubling of the core frequency. A challenge is that the rpi 5
>> requires a later kernel and L4S code hasn't been ported to those
>> versions yet. It would be good if L4S were available to this. Note:
>> One can use an rpi 4b in the interim for L4S testing.
>> https://urldefense.com/v3/__https://www.l4sgear.com/__;!!Hit2Ag!xk1Nfl
>> Cf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCeKyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A
>> 2n1r8M2_biSsNPMNQLJ7q8c$
>> <https://urldefense.com/v3/__https://www.l4sgear.com/__;!!Hit2Ag!xk1Nf
>> lCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCeKyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3
>> A2n1r8M2_biSsNPMNQLJ7q8c$ >
>> 
>> 
>> Thanks,
>> Bob
>>> Hello!
>>> 
>>> CableLabs and Kyrio are hosting an Interop·Labs Low Latency Low Loss
>>> Scalable Throughput (L4S) Interoperability Event, beginning Monday,
>>> February 26, and ending Friday, March 1, 2024 at the CableLabs office
>>> in Louisville, Colorado.
>>> 
>>> The high-level objectives of the event are to enable application
>>> developers, operating system developers, transport protocol designers
>>> and network equipment manufacturers to perform interoperability and
>>> functional testing of their L4S implementations.
>>> 
>>> During the “Interop·Lab” event, if we can identify additional
>>> interoperability features that are supported by the participants, we
>>> will encourage and support further interoperability testing where
>>> applicable. It should be noted that complete feature development is
>>> not required in order to participate in the event; participants are
>>> encouraged to participate even with limited feature functionality and
>>> non-final solution platforms.
>>> 
>>> Participating organizations should plan to have at least one person
>>> attend on-site for the event. We plan to allow remote connection into
>>> the Interop Lab for additional persons to interact with their
>>> equipment. We will utilize a Slack channel to allow open discussion
>>> between the participants and support staff, as we work through the
>>> testing.
>>> 
>>> Test Process and Guidelines for Participation Click here for
>>> Interop·Labs Process & Guidelines [1]
>>> 
>>> All in-person participants and those desiring remote connectivity
>>> must register for the event:
>>> https://urldefense.com/v3/__http://iplanprime.eventready.com/events/I
>>> nteropL4SFeb2024__;!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCe
>>> KyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN7Ou_AD0$
>>> <https://urldefense.com/v3/__http://iplanprime.eventready.com/events/
>>> InteropL4SFeb2024__;!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRC
>>> eKyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN7Ou_AD0$ > [2]
>>> 
>>> Registration deadline: February 21, 2024
>>> 
>>> Any questions about registration: Renae Cox [e-mail]
>>> <mailto:[e-mail]> Any questions about event: Greg White
>>> [e-mail] <mailto:[e-mail]>
>>> 
>>> Thanks!
>>> 
>>> CableLabs/Kyrio team
>>> 
>>> 
>>> 
>>> Links:
>>> ------
>>> [1]
>>> https://urldefense.com/v3/__https://iplanprime.eventready.com/files/I
>>> nteropL4SFeb2024/FEB*202024*20Guidelines*20Remote*20PHY*20Interop_.pd
>>> f__;JSUlJSU!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCeKyxoEcmy
>>> Z6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN4KcXj-E$
>>> <https://urldefense.com/v3/__https://iplanprime.eventready.com/files/
>>> InteropL4SFeb2024/FEB*202024*20Guidelines*20Remote*20PHY*20Interop_.p
>>> df__;JSUlJSU!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCeKyxoEcm
>>> yZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN4KcXj-E$ > [2]
>>> https://urldefense.com/v3/__http://iplanprime.eventready.com/events/I
>>> nteropL4SFeb2024__;!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCe
>>> KyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN7Ou_AD0$
>>> <https://urldefense.com/v3/__http://iplanprime.eventready.com/events/
>>> InteropL4SFeb2024__;!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRC
>>> eKyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMN7Ou_AD0$ >
> 
> --
> L4s-discuss mailing list
> [e-mail]
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/l4s-discuss__;!!Hit2Ag!xk1NflCf_bPDUFJ7x6VKVflIEMLubF9sxpbVUtRCeKyxoEcmyZ6OQcYcEliuuRA_BopEiNBmmf3A2n1r8M2_biSsNPMNJT-7ea0$