Differences

This shows you the differences between two versions of the page.

--- 0x13:reports:d1t1t04-hardware-offload-workshop [2019/04/03 21:07] – ehalep
+++ 0x13:reports:d1t1t04-hardware-offload-workshop [2019/09/28 17:04] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 The discussion started with the general switch ASIC offload and the many devlink updates, such as health Monitor, which monitors device health, and is used to pass information from the device to upper layer.
-There was a discussion about the need to have more hardware counter visibility for upper layers in the stack, right now the hardware has lots of stat counters, programmable ones but they are not tied well into the different layers in the stack.
+There was a discussion about the need to have more hardware counter visibility for upper layers in the stack. Right now the hardware has lots of stat counters, programmable ones but they are not tied well into the different layers in the stack.
 The discussion then shifted to packet drop visibility in the Control plane which is very important. The proposed solutions are:
@@ Line 28: / Line 28: @@
 The next talk was about Doorbell overflow recovery. The topic of discussion was the discovery and recovery for RDMA queues. Possible solutions were fast dequeuing, CPU stall and drop message detection and recovery procedures.
+This talk was followed with Qos Ingress Rate limiting and OVS offload with TC. The focus was on ingress rate limiting and policing. The rate limited was done with TC offload by adding a matchall type cls with police action and introducing reserved priorities. OVS should install Tc filters with priority offset, reserve higher priority for rate limiting.
+A possible issue with ovs-tc offload is when going from software to hardware, tc police is in software and filters are offloaded, this could break semanting. Possible solutions include reverting to original semantics of policing with offload isn't supported and ovs forcing tc filters in software only.
+Rony raised the question of why were priorities chosen vs chains. The answer was that recirculation is a good use case for chains.
-                    iii.     QoS offload for NIC eSwitch model: Focus on Ingress rate limiting and Policing.
+This was followed by a small test demo.
-.     Add a matchall type cls with police action
+Finally the last talk was about Scalable NIC HW offload. The talk begun with discussing the large amount of scaling hardware offloads.
+. Scale without using SRIOV
-.     Introduce reserved Priorities.
+. Multiple dynamic instances deployment at faster speed than VFs
+. NIC HW has very well defined vport based virtualization mode
-a.      OVS should install Tc filters with priority offset, reserve higher priority for rate limiting
+. One PCI device split into multiple smaller sub devices
+. Each sub device comes with own devices, vport, namespace resource
-.     Software-> hardware
+. Leverage mature switchdev mode and OVS eco-system
+. Applicable for SmartNIC use case.
-a.      Enable TC offload
+. Using rich vendor agnostic devlink iproute2 tool.
-b.     Add bridge and interfaces
-c.      Configure rate limit…translates to matchall filter with police action
-                                                         i.          Drop continue action
-d.     Configure OVS tc filters
-Rony: (why did you choose priorities vs chains…recirculation is a good use case for chains..)
-                  iv.     Scalable NIC HW offload (Or Garlitz, Parav Pandit)
-a.      Large amount of HW functions
-                                                         i.          Scale without using SRIOV
-                                                       ii.          Multiple dynamic instances deployment at faster speed than VFs
-                                                     iii.          NIC HW has very well defined vport based virtualization mode
-                                                     iv.          One PCI device split into multiple smaller sub devices
-                                                       v.          Each sub device comes with own devices, vport, namespace resource
-                                                     vi.          Leverage mature switchdev mode and OVS eco-system
-                                                   vii.          Applicable for SmartNIC use case.
-                                                 viii.          Use rich vendor agnostic devlink iproute2 tool
-                                                     ix.          Mdev software model view
-.     Mlx5 mdev devices
-.     Add control plane knob to add /query remove mdev devices
-a.      Devlink used
-.     Mentioned vDPA from Intel
-.     Create 3 devices, netdev, RDMA device and representor netdev.
-.     In HW mdev is attached to a vport
-.     Map it to a container…cannot be mapped to a VM since single instance of driver.
-                                                                                                      i.          Not connected to VFIO (it’s not necessary…), there is no buffer copy involved
-Site: https://www.netdevconf.org/0x13/session.html?workshop-hardware-offload
-Slides:
-Videos:
+The question that the presentors raised was how to achieve an Mdev software model view. A couple of points provided were:
+. Mlx5 mdev devices
+. Adding control plane knob to add /query remove mdev devices
+. Mentioned vDPA from Intel
+. Create 3 devices, netdev, RDMA device and representor netdev.
+. In HW mdev is attached to a vport
+. Map it to a container…cannot be mapped to a VM since single instance of driver.
+The talk was concluded with reasons it's been implemented that way, as the devlink tool and bus model fits requirements such as providing vendor agnostic solution and multi-port subdevice creation.
+Site: https://www.netdevconf.info/0x13/session.html?workshop-hardware-offload