Thanks, that's a good point.
Some applications such as ours, gains from this behaviour.
I was thinking about adding an mbox interface so that individual VF's may
be configured for loopback tx. By default, this configuration will be
disabled for all VF's.
Makes sense?
On Fri, Feb 13, 2015 at 3:34 PM, Alexander Duyck <
alexander.h.du...@redhat.com> wrote:
> On 02/13/2015 05:12 AM, Yotam Rubin wrote:
>
>> Just to clarify - enabling the PFVMTXSW register for a VF won't cause all
>> TX traffic to be looped back.
>> Rather, it will enable TX packets whose destination MAC address matches
>> the
>> VF's MAC address to be placed in the RX queue.
>> Is there a performance penalty enabling this?
>> If so, I can implement a new mbox API to allow individual VF's to decide
>> for themselves whether loopbacking is enabled for them.
>>
>> Yotam,
>>
>
> The problem is things like broadcast and multicast will be looped back to
> the original port. By filtering incoming traffic based on the source MAC
> address we avoid confusing the system by not letting it receive copies of
> its' own multicast and broadcast frames.
>
> - Alex
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
