0x13:reports:d2t1t06-veth-xdp-for-containers
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
0x13:reports:d2t1t06-veth-xdp-for-containers [2019/04/02 12:52] – ehalep | 0x13:reports:d2t1t06-veth-xdp-for-containers [2019/04/03 22:03] – ehalep | ||
---|---|---|---|
Line 4: | Line 4: | ||
Report by: Anjali Singhai | 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, 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/ | ||
+ | The generic from stack converts to skb to xdp_buff has high overhead | ||
- | 1. Performance wise little difference, then what is the point of doing native | + | 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. |
- | a. | + | The design was focused on Veth native XDP added rx queues and NAPI handler |
- | + | ||
- | b. Does not require allocation/ | + | |
- | + | ||
- | c. Native redirect converts to xdp_buff is very low overhead. | + | |
- | + | ||
- | d. | + | |
- | + | ||
- | e. Use case: | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | 1. Veth native XDP added rx queues and NAPI handler | + | |
- | + | ||
- | 2. This avoids | + | |
0x13/reports/d2t1t06-veth-xdp-for-containers.txt · Last modified: 2019/09/28 17:04 by 127.0.0.1