Re: [dpdk-dev] [PATCH v3 3/4] net/tap: add netlink back-end for flow API

2017-03-10 Thread Pascal Mazon
On Thu, 9 Mar 2017 15:29:01 + Ferruh Yigit wrote: > On 3/7/2017 4:35 PM, Pascal Mazon wrote: > > Each kernel netdevice may have queueing disciplines set for it, > > which determine how to handle the packet (mostly on egress). That's > > part of the TC (Traffic Control) mechanism. > > This is

Re: [dpdk-dev] [PATCH v3 3/4] net/tap: add netlink back-end for flow API

2017-03-09 Thread Ferruh Yigit
On 3/7/2017 4:35 PM, Pascal Mazon wrote: > Each kernel netdevice may have queueing disciplines set for it, which > determine how to handle the packet (mostly on egress). That's part of > the TC (Traffic Control) mechanism. This is nice. qdisc is egress part of the network stack right, is there any

[dpdk-dev] [PATCH v3 3/4] net/tap: add netlink back-end for flow API

2017-03-07 Thread Pascal Mazon
Each kernel netdevice may have queueing disciplines set for it, which determine how to handle the packet (mostly on egress). That's part of the TC (Traffic Control) mechanism. Through TC, it is possible to set filter rules that match specific packets, and act according to what is in the rule. This