From: "Waskiewicz Jr, Peter P" <redacted>
Date: Tue, 10 Jun 2008 12:55:16 -0700

The 802.1Qbb, per-priority pause (flow control), cannot work in a
software implementation.

Of course, I know that.

Also, the Rx filtering can't be emulated in software either.  The
MAC filters on VLAN priority.  I know that can be configured with
vconfig and set_ingress_map, but the whole point of the technology
is to have the Rx processing done in the hardware's packet buffers,
much like RSS filtering.

This is a scare crow, please don't use arguments like that.

Saying that it can't be done at all in software, but then saying
"well, it sort of can be done, but the point is to do it in hardware"
side-steps the very reason I want you to implement a software variant
of the parts that can be done in software.

This technology really is a hardware-based technology.

This sounds like another way of saying "having a software
implementation of even some of this facility would compromise
the value of our hardware implementation."

That's not the kind of decision making process we use when
deciding how to implement things in the kernel.