On Wed, Oct 16, 2013 at 12:47:13PM -0700, Adrian Chadd wrote:
A> .. so what brought this on? I can see this fixing issues for things where a
A> virtual device is created with taskqueues (eg a tap device of some sort)
A> that get stuffed into a vnet context. But for physical interfaces whose
A> task
On Wed, Oct 16, 2013 at 12:47:13PM -0700, Adrian Chadd wrote:
A> .. so what brought this on? I can see this fixing issues for things where a
A> virtual device is created with taskqueues (eg a tap device of some sort)
A> that get stuffed into a vnet context. But for physical interfaces whose
A> task
.. so what brought this on? I can see this fixing issues for things where a
virtual device is created with taskqueues (eg a tap device of some sort)
that get stuffed into a vnet context. But for physical interfaces whose
taskqueues don't have a specific vnet context and may need to set it
per-packe
