The NetDev conference wiki

User Tools

Site Tools

Trace:
0x13:reports:d2t1t06-veth-xdp-for-containers

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
0x13:reports:d2t1t06-veth-xdp-for-containers [2019/04/03 22:03] – ehalep0x13: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 Report by: Anjali Singhai
  
-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, then what is the point of doing native XDP for veth?  +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?  
-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. + 
-The generic from stack converts to skb to xdp_buff has high overhead+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. 
 + 
 +The generic from stack converting to skb to xdp_buff has high overhead.
  
 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. 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.
Line 12: Line 14:
 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. 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
-Site: https://www.netdevconf.org/0x13/session.html?talk-veth-xdp +
-Slides:  +
-Videos:  +
- +
0x13/reports/d2t1t06-veth-xdp-for-containers.1554329015.txt.gz · Last modified: 2019/09/28 17:04 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki