0x13:reports:d2t3t08-skb-meta-data-extensions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 0x13:reports:d2t3t08-skb-meta-data-extensions [2019/04/02 12:55] – ehalep | 0x13:reports:d2t3t08-skb-meta-data-extensions [2019/09/28 17:04] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Day 2 / Track 3 / Talk 8 | + | Day 2 / Common |
| Talk – Nuts-n-Bolts: | Talk – Nuts-n-Bolts: | ||
| Speakers: Florian Westphal | Speakers: Florian Westphal | ||
| Report by: Kiran Patil | Report by: Kiran Patil | ||
| - | Since the beginning, it has been challenge to pass additional information without | + | Since the beginning, it has been a challenge to pass additional information without |
| - | increasing the size of sk_buff. This session outlines the details about | + | Sk_buff structure has been extended by adding 2 fields, first field indicates whether there are any active extensions present or nor and other field points to ' |
| - | how SKB meta data extensions are designed | + | This talks also explains the need of such feature, which came primarily due to the need of "meta data" about data (which is expressed in in sk_buff). This feature is being used by ispec(xfrm), |
| - | meta data extension. | + | Question: Is it OK to use this SKB meta-data extension infrastructure for carrying out information in case of tunnel? |
| - | + | ||
| - | + | ||
| - | + | ||
| - | sk_buff structure has been extended by adding 2 fields, first field indicates | + | |
| - | + | ||
| - | whether there are any active extensions present or nor and other field | + | |
| - | + | ||
| - | points to ' | + | |
| - | + | ||
| - | such as memory for it comes from dedicated cache pool (kmem_cache). This skb_ext | + | |
| - | + | ||
| - | blob is managed thru' ref_count. skb_ext memory is freed when SKB is freed. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | This talks also explains the need of such feature, which came primarily due | + | |
| - | + | ||
| - | to the need of "meta data" about data (which is expressed in in sk_buff). | + | |
| - | + | ||
| - | This feature is being used by ispec(xfrm), | + | |
| - | + | ||
| - | (planned for future). In MPTCP, there is need of map logical sequence | + | |
| - | + | ||
| - | number to tcp sequence number used by individual flows. This talk also discusses | + | |
| - | + | ||
| - | when to use SKB extensions. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | Question: Is it OK to use this SKB meta-data extension infrastructure for carrying | + | |
| - | + | ||
| - | out information in case of tunnel? | + | |
| - | + | ||
| - | Answer: It's OK to use skb meta-data extension mechanism to carry/ | + | |
| - | + | ||
| - | any meta-data about data. | + | |
| - | + | ||
| - | + | ||
| - | Site: https:// | + | |
| - | Slides: | + | |
| - | Videos: | + | |
| + | Answer: It's OK to use skb meta-data extension mechanism to carry/pass any meta-data about data. | ||
| + | Site: https:// | ||
0x13/reports/d2t3t08-skb-meta-data-extensions.1554209713.txt.gz · Last modified: 2019/09/28 17:04 (external edit)