October 2023 - people - netdevconf.info

0x17: talk, Quantum-Proofing Data: The Power Of Post-Quantum Cryptography
by Jamal Hadi Salim 04 Oct '23

04 Oct '23

Quantum computing presents a potential threat of being able to compromise existing cryptographic techniques. Shor's algorithm has the potential to break the RSA and Elliptic Curve Diffie-Hellman algorithms, both of which are pivotal for key exchange in Transport Layer Security (TLS). Our speaker, Milena Olech, says the solution is to adopt post-quantum cryptography (PQC) algorithms. In this talk Milena outlines the mathematical foundation of the CRYSTALS-Kyber algorithm and illustrates its application in the TLS handshake. In order to assess the efficacy of PQC, Milena will detail a comprehensive comparison between traditional cryptographic methods and post-quantum alternatives and provide a condensed summary of the comparison. cheers, jamal Reminder: Three days to go before early-bird registration ends!

1 0

Register now please!
by Jamal Hadi Salim 03 Oct '23

03 Oct '23

Just a reminder 5 more days to go for early bird registration. Also a reminder this is a hybrid conference; nothing can beat physical get together but you can participate virtually as well. Early registration helps us plan better. See: https://netdevconf.info/0x17/pages/registration.html cheers, jamal

1 0

0x17: talk, Integrating eBPF Into The P4TC Datapath
by Jamal Hadi Salim 03 Oct '23

03 Oct '23

P4TC was first introduced in 0x16[1]. After the first RFC was posted on the list, some of the community feedback made was to convert the s/w datapath from a scriptable (ala tc u32) to instead make use of eBPF with a strong argument being made that the s/w data path will be more performant. In this talk Jamal Hadi Salim et al will discuss the new architecture which factors in eBPF as the software datapath. The talk will go into the P4TC architecture factoring in eBPF and the pros and cons of this change from a scriptable approach. Jamal (twit that horn here) will further discuss the uapi and the kernel code architecture. There have been several RFC postings in the last 9 months[2] and it is expected the upstreaming efforts will start in the near future. cheers, jamal [1]https://netdevconf.info/0x16/session.html?Your-Network-Datapath-Will-Be-P4-Scripted [2] latest at this posting can be found here: https://lore.kernel.org/netdev/20230930143542.101000-1-jhs@mojatatu.com/

1 0

0x17: talk, Firewall and Service Tickets (FAST)
by Jamal Hadi Salim 02 Oct '23

02 Oct '23

There is no good standardized way for applications to signal the network for services, like QoS, that the app wants applied to their packets. Typically it is some sys admin that decides how these services and resources are partitioned and configures their control. Enter FAST - which is being developed at the IETF. Tom Herbert says FAST is secure, expressive, stateless, not spoofable, deployable, efficient, dynamic, requires no DPI, doesn’t disclose internals of the network, and works with any transport protocol. FAST tickets are attached to packets to describe the service requests and grants of admission that the application has requested from the network. Tickets are sent in IPv6 Hop-by-Hop options. Tom will provide rationale why Hop-by-Hop options are really the best choice compared to proposed alternatives despite concerns about them being dropped in the Internet. Eventually Tom will present the kernel patches and tie them to how applications will use the provided infra to request for tickets and how they are granted, how they're set and transmitted in packets, how a network node can process the FAST ticket in the packet and apply network mechanisms to satisfy the service requests. cheers, jamal PS: 5 more days left for early-bird registration. visit netdevconf.info/0x17/registration

1 0

[RESEND]0x17: Talk, Congestion control architecture for host congestion
by Jamal Hadi Salim 02 Oct '23

02 Oct '23

Apologies, I left out the subject line in the last email, so resending this... Link speeds are going up at an incredible rate. Cloud vendors are already asking for 4-800Gbps. Unfortunately the rest of the host hardware infra is not keeping up. Even at the "low low speed;->" of 100Gbps the host CPU speeds, cache sizes, memory access latency, memory bandwidth per core, NIC buffer sizes, are just overwhelmed. As an example 6 CPU cores can saturate all available memory bandwidth - imagine being on a machine that has 56C(112 hyperthreads).... In this talk, Saksham Agarwal, Arvind Krishnamurthy and Rachit Agarwal say that this has brought in new trends not seen before: congestion within the processor, memory and peripheral interconnects of the host which of course causes back pressure all the way to the NIC - meaning back to the network and, alas, causes congestion within the network. Testing with Linux DCTCP shows that host congestion by our speakers found as much as 1% packet drops at the host, 35-55% throughput degradation, and 120-5000x tail latency inflation! Agarwal et al want us to look closely at more than just network heuristics to resolve this emerging challenge. As an example: applications generating CPU-to-memory traffic and clogging the memory bus are currently not considered as part of the congestion control calculus at all - even though they are most certainly part of the culprits. In this talk our esteemed speakers introduce what they call "hostcc" as a response to these challenges. Hostcc makes about ~800 line kernel code changes. A little bit more details: https://netdevconf.info/0x17/6 For the real meat-and-potatoes come to the talk of course! cheers, jamal PS: 5 more days left for early-bird registration. visit netdevconf.info/0x17/registration

1 0

0x17: Talk,
by Jamal Hadi Salim 02 Oct '23

02 Oct '23

Link speeds are going up at an incredible rate. Cloud vendors are already asking for 4-800Gbps. Unfortunately the rest of the host hardware infra is not keeping up. Even at the "low low speed;->" of 100Gbps the host CPU speeds, cache sizes, memory access latency, memory bandwidth per core, NIC buffer sizes, are just overwhelmed. As an example 6 CPU cores can saturate all available memory bandwidth - imagine being on a machine that has 56C(112 hyperthreads).... In this talk, Saksham Agarwal, Arvind Krishnamurthy and Rachit Agarwal say that this has brought in new trends not seen before: congestion within the processor, memory and peripheral interconnects of the host which of course causes back pressure all the way to the NIC - meaning back to the network and, alas, causes congestion within the network. Testing with Linux DCTCP shows that host congestion by our speakers found as much as 1% packet drops at the host, 35-55% throughput degradation, and 120-5000x tail latency inflation! Agarwal et al want us to look closely at more than just network heuristics to resolve this emerging challenge. As an example: applications generating CPU-to-memory traffic and clogging the memory bus are currently not considered as part of the congestion control calculus at all - even though they are most certainly part of the culprits. In this talk our esteemed speakers introduce what they call "hostcc" as a response to these challenges. Hostcc makes about ~800 line kernel code changes. A little bit more details: https://netdevconf.info/0x17/6 For the real meat-and-potatoes come to the talk of course! cheers, jamal PS: 5 more days left for early-bird registration. visit netdevconf.info/0x17/registration

1 0

0x17: Talk, NIC offloads at Hyperscale: experience, new offloads and validation
by Jamal Hadi Salim 01 Oct '23

01 Oct '23

Willem de Bruijn says that lack of clear operating conditions, vague feature definitions and dearth of publicly available tests makes it hard to deploy at scale NIC offloads from multiple vendors. Issues seen in deployments range from inconsistency between devices, scalability limits, incompatibility with real production workloads, and simply hardware bugs; even a commodity offload as a checksum is not as well defined if you look across multiple vendor implementations. Willem will discuss why providing a way to define these offloads precisely, in a way that scales and avoids common bugs, while combining expertise from multiple vendors and users is the way to go. More importantly he believes that sharing all those details in an open and unencumbered format would help alleviate if not solve the current wild-west approach. The effort is currently housed under the auspices of the "OCP NIC Core Offloads specifications". Willem will go over some critical offloads, from established to novel ongoing work, such as pacing and inline crypto and show how they can fail in practice. And last but not least provide an overview of some of the testcases which have already been contributed to the kernel tree including tests for RSS, HW-GRO, TSO and others. cheers, jamal PS: 6 more days left for early-bird registration. visit netdevconf.info/0x17/registration

1 0

0x17: talk, Improving multi-phy and multi-port interfaces
by Jamal Hadi Salim 01 Oct '23

01 Oct '23

How do we deal with a single MAC connected to multiple PHYs - whether chained or in parallel - with multiple front-facing ports? What about when multiple front facing ports utilizing a single PHY or, fun, multiple PHYs? Maxime Chevallier we have some support for these scenarios today where we hide the PHY behind a netdev. The consequences are there is no way to config an individual PHY when multiple PHYs are present on a link - think SFP transceivers for example. Selecting which front-facing port to use is also limited. In this talk, Maxime will describe ongoing work to support these complex topologies, the challenges faced and expected improvements. cheers, jamal PS: 6 more days left for early-bird registration. visit netdevconf.info/0x17/registration

1 0