The net sched infrastructure has a gso ptr that points to skb structs
that have failed to be enqueued by the device driver.
This can happen when multiple cores try to push a skb onto the same
underlying hardware queue resulting in lock contention. This case is
handled by a cpu collision handler
On Wed, 30 Dec 2015 09:52:49 -0800
John Fastabend wrote:
> The net sched infrastructure has a gso ptr that points to skb structs
> that have failed to be enqueued by the device driver.
What about fixing up the naming "gso" to something else like "requeue",
in the
On 15-12-30 12:26 PM, Jesper Dangaard Brouer wrote:
> On Wed, 30 Dec 2015 09:52:49 -0800
> John Fastabend wrote:
>
>> The net sched infrastructure has a gso ptr that points to skb structs
>> that have failed to be enqueued by the device driver.
>
> What about fixing up