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

[Adrian Chadd]

.. 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-packet, what may this break?

Ie - what did this fix, and why isn't it being fixed in all the various
taskqueues in device drivers?

I'd rather not see the taskqueue setup (which knows nothing about network
contexts at all) grow this just to solve a bunch of places where the task
in question can just correctly initialise the context itself when it's
called.

Thanks,



-adrian