Re: [PATCH net-next 4/4] xps_flows: XPS for packets that don't have a socket

2016-09-01 Thread Alexander Duyck
On Thu, Sep 1, 2016 at 8:56 AM, Tom Herbert wrote: > On Thu, Sep 1, 2016 at 8:36 AM, Alexander Duyck > wrote: >> On Wed, Aug 31, 2016 at 5:10 PM, Tom Herbert wrote: >>> xps_flows maintains a per device flow table that is indexed by the >>> skbuff hash. The table is only consulted when there is n

Re: [PATCH net-next 4/4] xps_flows: XPS for packets that don't have a socket

2016-09-01 Thread Tom Herbert
On Thu, Sep 1, 2016 at 8:36 AM, Alexander Duyck wrote: > On Wed, Aug 31, 2016 at 5:10 PM, Tom Herbert wrote: >> xps_flows maintains a per device flow table that is indexed by the >> skbuff hash. The table is only consulted when there is no queue saved in >> a transmit socket for an skbuff. >> >>

Re: [PATCH net-next 4/4] xps_flows: XPS for packets that don't have a socket

2016-09-01 Thread Alexander Duyck
On Wed, Aug 31, 2016 at 5:10 PM, Tom Herbert wrote: > xps_flows maintains a per device flow table that is indexed by the > skbuff hash. The table is only consulted when there is no queue saved in > a transmit socket for an skbuff. > > Each entry in the flow table contains a queue index and a queue

[PATCH net-next 4/4] xps_flows: XPS for packets that don't have a socket

2016-08-31 Thread Tom Herbert
xps_flows maintains a per device flow table that is indexed by the skbuff hash. The table is only consulted when there is no queue saved in a transmit socket for an skbuff. Each entry in the flow table contains a queue index and a queue pointer. The queue pointer is set when a queue is chosen usin