svn commit: r256587 - in head/sys: kern sys

[Gleb Smirnoff]

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> taskqueues don't have a specific vnet context and may need to set it
A> per-packet, what may this break?
A> 
A> Ie - what did this fix, and why isn't it being fixed in all the various
A> taskqueues in device drivers?
A> 
A> I'd rather not see the taskqueue setup (which knows nothing about network
A> contexts at all) grow this just to solve a bunch of places where the task
A> in question can just correctly initialise the context itself when it's
A> called.

Also, see

http://lists.freebsd.org/pipermail/svn-src-head/2013-October/052359.html

-- 
Totus tuus, Glebius.