Difference between revisions of "Networking/NIC Software"

From OpenCompute
Jump to: navigation, search
(Get Involved)
(initial summary)
Line 4: Line 4:
 
:Welcome to the OCP '''Networking NIC Software''' Sub-Project.
 
:Welcome to the OCP '''Networking NIC Software''' Sub-Project.
  
 +
Our goal is to bring together NIC vendors and hyperscaler and other users to spur discussion about relevant NIC features, and arrive at agreed concrete specs for interface and behavior.
 +
 +
We aim to ensure that all vendor implementations conform to the actual business requirements of large users. These requirements have historically often been underspecified or shared only with individual vendors.
 +
 +
For each feature, we aim to arrive at a clear specification that covers both driver API and behavioral elements, such as scalability and performance expectations. Additionally, we aim to publish concrete conformance tests that vendors can use to self-certify.
 +
 +
===Charter===
 +
 +
The focus is on foundational NIC features.
 +
 +
Significant developments are taking place in SmartNICs. For now, features not strictly related to the core network transmit and receive path are out of scope for this subproject. This includes on-board co-processors, control plane offload and offload of non networking interfaces, such as NVME (storage).
 +
 +
===Public===
 
:This Sub-Project is open to the public and we want to welcome all those who would like to be involved.
 
:This Sub-Project is open to the public and we want to welcome all those who would like to be involved.
  
Line 10: Line 23:
 
==Documents==
 
==Documents==
  
:- [https://146a55aca6f00848c565-a7635525d40ac1c70300198708936b4e.ssl.cf1.rackcdn.com/files/cf9682dad2e1e654c19580df07fdbee0cab63dbc.pdf Charter]
+
:- [https://2021ocpglobal.fnvirtual.app/a/event/1996 NICs for Hyperscale Deployments]: 2021 OCP Global Summit introductory presentation
:- OCP Presentation Template - please contact [mailto:michael@opencompute.org Michael Schill] or [mailto:archna@opencompute.org Archna Haylock] for a copy
+
 
 +
==Topics==
 +
 
 +
The area is open for innovation, and new topics are encouraged.
 +
 
 +
The current list of active topics are
 +
 
 +
====Telemetry====
 +
Define a standard set of network device and queue statistics, with standard names and unambiguous definition of each statistic's meaning.
 +
 
 +
For Linux based deployments, this builds on and extends the standard '''rtnl_link_stats64''' and replaces much of the free-form current driver interface exposed through '''ethtool -S'''.
 +
 
 +
===Traffic Engineering===
 +
Standardize state-of-the-art TE mechanisms.
 +
 
 +
Develop common support for stateless [https://www.kernel.org/doc/html/latest/networking/segmentation-offloads.html#generic-segmentation-offload generic tunneling offload]: combine TCP segmentation offload (an indispensible offload for many workloads) with arbitrary tunnel protocols, instead of building an offload for each tunnel protocol. Because hyperscalers may use protocols, protocol stacks and protocol variants --proprietary or not-- that the vendor cannot always anticipate.
 +
 
 +
Develop industry standard support for [https://legacy.netdevconf.info/0x12/session.html?evolving-from-afap-teaching-nics-about-time Earliest Departure Time] (EDT) stateless rate limiting offload.
 +
 
 +
====Flow Steering====
 +
Device queues are the basis for scalable networking, as well as task isolation and userspace queues.
 +
 
 +
Define
 +
# a common interface for configuring devices queues and RSS groups, including dynamically without device down.
 +
# a common interface for steering flows to queue (groups), including expectations on datapath performance and scalability.
 +
 
 +
Additionally, define
 +
# a common queue interface for userspace network stacks like DPDK and [https://research.google/pubs/pub48630/ Google SNAP].
 +
 
 +
 
  
 
==Project Leadership==
 
==Project Leadership==

Revision as of 18:28, 4 April 2022

OCP-networking-v1-17a3x.png

Welcome

Welcome to the OCP Networking NIC Software Sub-Project.

Our goal is to bring together NIC vendors and hyperscaler and other users to spur discussion about relevant NIC features, and arrive at agreed concrete specs for interface and behavior.

We aim to ensure that all vendor implementations conform to the actual business requirements of large users. These requirements have historically often been underspecified or shared only with individual vendors.

For each feature, we aim to arrive at a clear specification that covers both driver API and behavioral elements, such as scalability and performance expectations. Additionally, we aim to publish concrete conformance tests that vendors can use to self-certify.

Charter

The focus is on foundational NIC features.

Significant developments are taking place in SmartNICs. For now, features not strictly related to the core network transmit and receive path are out of scope for this subproject. This includes on-board co-processors, control plane offload and offload of non networking interfaces, such as NVME (storage).

Public

This Sub-Project is open to the public and we want to welcome all those who would like to be involved.

Disclaimer: Please do not submit any confidential information to the Project Community. All presentation materials, proposals, meeting minutes and/or supporting documents are published by OCP and are open to the public in accordance to OCP's Bylaws and IP Policy. This can be found on the OCP OCP Policies page. If you have any questions please contact OCP.

Documents

- NICs for Hyperscale Deployments: 2021 OCP Global Summit introductory presentation

Topics

The area is open for innovation, and new topics are encouraged.

The current list of active topics are

Telemetry

Define a standard set of network device and queue statistics, with standard names and unambiguous definition of each statistic's meaning.

For Linux based deployments, this builds on and extends the standard rtnl_link_stats64 and replaces much of the free-form current driver interface exposed through ethtool -S.

Traffic Engineering

Standardize state-of-the-art TE mechanisms.

Develop common support for stateless generic tunneling offload: combine TCP segmentation offload (an indispensible offload for many workloads) with arbitrary tunnel protocols, instead of building an offload for each tunnel protocol. Because hyperscalers may use protocols, protocol stacks and protocol variants --proprietary or not-- that the vendor cannot always anticipate.

Develop industry standard support for Earliest Departure Time (EDT) stateless rate limiting offload.

Flow Steering

Device queues are the basis for scalable networking, as well as task isolation and userspace queues.

Define

  1. a common interface for configuring devices queues and RSS groups, including dynamically without device down.
  2. a common interface for steering flows to queue (groups), including expectations on datapath performance and scalability.

Additionally, define

  1. a common queue interface for userspace network stacks like DPDK and Google SNAP.


Project Leadership

Incubation Committee Representative

- Jason Forrester (Target)

Sub-Project Leads

- Jakub Kicinski (Meta)
- Willem de Bruijn (Google)

Get Involved

- Main Networking Project Mailing List
- OCP website
- OCP Calendar

Regular Project Calls

TBD

This page has:

- the agenda for upcoming calls
- complete information on how to join the call
- minutes from past calls.

Recordings from Past Calls

Specs and Designs

Link to the Specs and Designs page -http://www.opencompute.org/wiki/Networking/SpecsAndDesigns

Past Workshops