ARM Mini-Summit - OpenDataPlane Monarch Release - Linaro

1. Presented by
Date
Bill Fischofer
21 June 2016
OpenDataPlane (ODP)
Introducing ODP Monarch
ARM Ecosystem Mini Summit Berlin
Event

2. ● Requirements that motivate and drive ODP
● What is ODP?
● Sponsorship and governance model
● Components
● Structure
● ODP Monarch Features, Platforms, and Applications
Discussion Topics

3. ● Support application portability across diverse ISAs and system
architectures
○ Core counts, memory organization, integrated HW capabilities, etc.
OpenDataPlane Requirements
● Be able to exploit platform-specific acceleration and offload
capabilities (HW and SW) without application effort
○ e.g., HW buffer/packet mgmt, integrated I/O, HW parsing and classification, HW
scheduling and flow ordering, HW egress traffic shaping and QoS, etc.
● Support scalability to many-core architectures without application
redesign
○ Application design unchanged if running on 4, 40, or 400 cores

4. ODP Overview

5. The Linaro Networking Group and
its 13 member companies are
sponsors and upstream
maintainers of ODP
LNG membership is open to all
ODP is fully open source and open
contribution, uses BSD 3-clause
licensing
All ODP design work is carried out
in public with both open face-to-
face meetings and weekly public
architecture calls, and on the ODP
mailing list
ODP Sponsorship and Governance

6. What is OpenDataPlane?
An Abstract API Specification
Multiple independently maintained
implementations of the ODP API
Validation Test Suite
ODP API Specification
ODP Implementations
ODP
Validation
Test Suite

7. The ODP API Specification
ODP API
Specification
An Abstract API Specification
● Vendor and platform neutral
● Application-centric--covers functional needs of data plane applications
● Ensures portability by specifying functional behavior of ODP
● Defined jointly and openly by application writers and platform implementers
● Architected to be implementable on a wide range of platforms efficiently
● Sponsored, Governed, and Maintained by Linaro Networking Group (LNG)

8. ODP Implementations
Multiple independently maintained
implementations of the ODP API
● One size does not fit all--widely differing internals among platforms
● Anyone can create an ODP implementation tailored to their platform
● Distribution and maintenance of each implementation as owner wishes
○ Open source or closed source as business needs determine
○ Have independent release cycles and service streams
● Allows HW and SW innovation in how ODP APIs are implemented on each
platform
ODP Implementations

9. ODP Implementations (Cont’d)
LNG distributes and maintains a number
of Reference Implementations of ODP
● Provide easy bootstrapping of ODP onto new platforms
● Implementers free to borrow or tailor code as needed for their platform
● Implementers retain full control over their own implementations whether or
not they are derived from a reference implementation
ODP Implementations
odp-linux odp-dpdk
● Runs on any linux kernel
● Not a performance target
● ODP APIs mapped on top of DPDK
● Performance target for x86 systems

10. ODP Validation Test Suite
ODP
Validation
Test Suite
Validation Test Suite
● Synchronized with ODP API Specification level
● Maintained and distributed by LNG
● Open source, open contribution, BSD-3 licensed
● Key to ensuring application portability across all ODP
implementations
● Tests that implementations of ODP conform to the specified
functional behavior of ODP APIs
● Can be run at any time by both users and vendors to validate
implementations of ODP

11. ODP Monarch Overview

12. Community of ODP
Applications
ODP Application
Platform AOCTEON
ODP API
QorIQ - DPAA
Application can run on any Platform
SDK A
Simple
Executive
Freescale SDK DPDK
X86
Why ODP? - Application View
ODP demonstrated
to add negligible
overhead vs. native
SDKs

13. Why ODP? - Platform Vendor View
New
SoC/Platform
Platform can compete for any Socket
Application AOpenVswitch Proxy
ODP API
SDK
Network Stack
Open source value

14. ODP Project History
● October, 2013: Announced at LCU ‘13
● 2014: Preview releases (v0.1 - v0.11)
● 2015: Pre-Production Evaluation releases (v1.0 -
v1.11)
● 2016: Production Release: “Monarch”
○ First Long Term Stable (LTS) ODP release
○ Focus on embedded apps and OPNFV support
○ Support higher-level adjunct projects like OpenFastPath
○ Support for acceleration for other projects like NGiNX, Snabb Switch,
etc.

15. ODP Monarch Programming Model
Application logic
ODP Framework

16. ODP Platforms
Datacenter Servers
● X86 + NIC
● ARMv8 64-bit server grade CPUs
Embedded Systems
● SoCs
● Broadcom, Cavium, Huawei, Kalray, Marvell, Mellanox, NXP,
TI, ...
● ARM (v7 and v8), MIPS, Power ISAs

17. ODP Application Areas
NFV Infrastructure
● Smart NICs
● Virtual switch acceleration
Appliances / Embedded
● Switches, routers, base stations, etc.
VNF Virtual Network Functions

18. Summary: ODP Advantages
● A framework for data plane applications
○ Portable
○ Accelerated
○ Scalable
● Open source, open contribution, open governance
● Stable APIs validated and supported across many
platforms suitable for many market segments
● Non-exclusive--can mix with other APIs as needed
● Flexible programming models, supporting both polling
and event-driven application design

19. Thank you