.. 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
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
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
Author: glebius
Date: Wed Oct 16 05:02:01 2013
New Revision: 256587
URL: http://svnweb.freebsd.org/changeset/base/256587
Log:
For VIMAGE kernels store vnet in the struct task, and set vnet context
during task processing.
Reported tested by: mm
Modified:
head/sys/kern/subr_taskqueue.c
