User Tools

Site Tools


0x13:reports:d1t1t03-traffic-control-workshop

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:d1t1t03-traffic-control-workshop [2019/04/08 20:58] ehalep0x13:reports:d1t1t03-traffic-control-workshop [2019/09/28 17:04] (current) – external edit 127.0.0.1
Line 4: Line 4:
 Report by: Jamal Hadi Salim Report by: Jamal Hadi Salim
  
-This workshop is a regular fixture at the netdev conference +This workshop is a regular fixture at the netdev conference to discuss ongoing issues, experiences, new features and proposals.
-to discuss ongoing issues, experiences, new features and +
-proposals.+
  
-contributor: Vlad Buslov(Mellanox)+contributor: Vlad Buslov
 topic:  Unlocking TC rules update API: challenges and lessons learned. topic:  Unlocking TC rules update API: challenges and lessons learned.
  
-Vlad Discussed his ongoing work on removing locks from the TC +Vlad Discussed his ongoing work on removing locks from the TC rules control path in order to improve update rates. Vlad hopes that when he is done he can improve the infrastructure by having multiple control path updates happening concurrently. In general Vlad discussed his challenges and lessons he learned while progressing on this work.
-rules control path in order to improve update rates. +
-Vlad hopes that when he is done he can improve the infrastructure +
-by having multiple control path updates happening concurently. +
-In general+
-Vlad discussed his challenges and lessons he learnt while progressing +
-on this work.+
  
-Contributors: Amritha Nambiar, Anjali Singhai and Sridhar Samudrala(Intel)+Contributors: Amritha Nambiar, Anjali Singhai and Sridhar Samudrala
 Topic: Intel TC Hardware Offload Updates Topic: Intel TC Hardware Offload Updates
  
-Amritha talked in details about the work done and challenges encountered +Amritha talked in details about the work done and challenges encountered for creating port range expressions for the Flower classifier. She then proceeded to describe new work done on ixgbe for the u32 classifiernamely new actions created (skbedit on mark and accept/ok) as well as ability to
-for creating port range expressions for the Flower classifier. She then +
-proceeded to describe new work done on ixgbe for the u32 classifier namely +
-new actions created (skbedit on mark and accept/ok) as well as ability to+
 define queue selection based on flowid/classid definition. define queue selection based on flowid/classid definition.
  
-Anjali went on to describe future work to introduce stats on a per +Anjali went on to describe future work to introduce stats on a per filter basis based on policy and intention to add policer work. She talked about challenges with Flower having named fields which always require kernel changes; rules being cached at many layers (user space, kernel, hardware) and last described intention to take advantage of Vlad's work optimizing rule update to 500K/sec for Intel hardware.
-filter basis based on policy and intention to add policer work. She talked +
-about challenges with Flower having named fields which always require +
-kernel changes; rules being cached at many layers (user space, kernel, +
-hardware) and last described intention to take advantage of Vlad's work +
-optimizing rule update to 500K/sec for Intel hardware.+
  
-Contributor: Andy Gospodarek(Broadcom)+Contributor: Andy Gospodarek
 Topic: Stats offload transfers Topic: Stats offload transfers
  
-Andy discussed the challenges of offloaded TC stats in presence +Andy discussed the challenges of offloaded TC stats in presence of a large number(millions) of rules/actions; Many use cases (such as billing or SLA validations) require frequent updates from hardware at a higher frequency which are not efficient (true for software as well). Several approaches were discussed. This will be an ongoing discussion.
-of a large number(millions) of rules/actions; Many use cases (such as billing +
-or SLA validations) require frequent updates from hardware +
-at a higher frequency which are not efficient (true for software as +
-well). Several approaches were discussed. This will be an ongoing discussion.+
  
 Contributor: John Hurley (Presented by Simon Horman) Contributor: John Hurley (Presented by Simon Horman)
 Topic: Offloading TC rules on OVS Internal Ports Topic: Offloading TC rules on OVS Internal Ports
  
-Simon described a challenge in regards to semantics used by +Simon described a challenge in regards to semantics used by "OVS Internal Ports"; internal ports send packets directly to the stack and bypass TC ingress(and therefore miss offloading opportunity presented by TC). Several proposals were made to address these issues.
-"OVS Internal Ports"; internal ports send packets directly +
-to the stack and bypass TC ingress(and therefore miss offloading +
-opportunity presented by TC). Several proposals were made to +
-to address these issues.+
  
-Contributor: Lucas Bates (Mojatatu)+Contributor: Lucas Bates 
 Topic: Testing Developments for TDC Topic: Testing Developments for TDC
  
-Lucas described a new tdc feature for traffic +Lucas described a new tdc feature for traffic generation using scappy. He then proceeded to give 
-generation using scappy. He then proceeded to give +a demo on its usage. The goal of the feature is to be able to produce arbitrary packets that can test classifier rules.
-a demo on its usage. The goal of the feature is to be +
-able to produce arbitrary packets that can test classifier +
-rules. +
- +
-Contributor: Roman Mashak (Mojatatu) +
-Roman described the Quota Enforcement(QE) action which is to +
-be upstreamed. QE is used in telco environments to provide a +
-limit on bytes consumed during a policy lifetime +
-(think your monthly 4GB data plan) +
- +
-Site: https://www.netdevconf.org/0x13/session.html?workshop-Traffic-Control +
-Slides:  +
-Videos: +
  
 +Contributor: Roman Mashak 
 +Roman described the Quota Enforcement(QE) action which is to be upstreamed. QE is used in telco environments to provide a limit on bytes consumed during a policy lifetime (think your monthly 4GB data plan)
  
 +Site: https://www.netdevconf.info/0x13/session.html?workshop-Traffic-Control
0x13/reports/d1t1t03-traffic-control-workshop.1554757130.txt.gz · Last modified: 2019/09/28 17:04 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki