Differences

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

--- 0x13:reports:d2t1t06-veth-xdp-for-containers [2019/04/02 12:52] – ehalep
+++ 0x13:reports:d2t1t06-veth-xdp-for-containers [2019/09/28 17:04] (current) – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 Report by: Anjali Singhai
-Veth XDP: generic vs native
+This talk was about XDP for containers. It begun with a description about what the XDP is and then went on to discuss the generic vs native. The question raised by the presenter was that since performance wise there is little difference, what is then the point of doing native XDP for veth?
-.     Performance wise little difference, then what is the point of doing native XDP for veth?
+The presenter made several points, such as XDP_REDIRECT (can be done without allocating skb_buff, using xdp_frame), no requirement to allocation/free of additional meta data buffer, native redirect converted to xdp_buff has very low overhead.
-a.      The point is XDP_REDIRECT (can be done without allocating skb_buff, using xdp_frame)
+The generic from stack converting to skb to xdp_buff has high overhead.
-b.     Does not require allocation/free of additional Meta data buffer
+Several use case were described. First XDP in containers, where a container can install its own XDP program and use container to container using xdp_redirect. Second was program chaining where a program can be called from another program.
-c.      Native redirect converts to xdp_buff is very low overhead.
-d.     Generic from stack converts to skb to xdp_buff which is high overhead
-e.      Use case:
-                                                                             i.     Containers, Container can install its own XDP program and use container to container using xdp_redirect
-                                                                           ii.     Program chaining
-.     Veth native XDP added rx queues and NAPI handler
-.     This avoids infinite loop and stack overflow due to misconfigured XDP_redirect chain.
-Site: https://www.netdevconf.org/0x13/session.html?talk-veth-xdp
-Slides:
-Videos:
+The design was focused on Veth native XDP added rx queues and NAPI handler which avoided infinite loop and stack overflow due to misconfigured XDP_redirect chain.
+Site: https://www.netdevconf.info/0x13/session.html?talk-veth-xdp