User Tools

Site Tools


0x13:reports:d2t3t08-skb-meta-data-extensions

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:d2t3t08-skb-meta-data-extensions [2019/04/08 15:06] ehalep0x13: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 / Talk 8+Day 2 / Common Track / Talk 8
 Talk – Nuts-n-Bolts: Skb Meta Data Extensions Talk – Nuts-n-Bolts: Skb Meta Data Extensions
 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 increasing the size of sk_buff. This session outlines the details about how SKB meta data extensions are designed (inner working), and when to use the meta data extension.+Since the beginning, it has been challenge to pass additional information without increasing the size of sk_buff. This session outlines the details about how SKB meta data extensions are designed (inner working), and when to use the meta data extension.
  
-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 'active_extension' (aka skb_ext). Skb_ext has several advantages 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.+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 'active_extension' (aka skb_ext). Skb_ext has several advantages such as memory for it comes from dedicated cache pool (kmem_cache). This skb_ext blob is managed through 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), bridge netfilter, and Multipath TCP (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. 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), bridge netfilter, and Multipath TCP (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.
Line 14: Line 14:
 Answer: It's OK to use skb meta-data extension mechanism to carry/pass any meta-data about data. Answer: It's OK to use skb meta-data extension mechanism to carry/pass any meta-data about data.
  
-Site: https://www.netdevconf.org/0x13/session.html?skb-meta-data-extensions +Site: https://www.netdevconf.info/0x13/session.html?skb-meta-data-extensions
-Slides:  +
-Videos:  +
- +
0x13/reports/d2t3t08-skb-meta-data-extensions.1554735967.txt.gz · Last modified: 2019/09/28 17:04 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki