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,
On Thu, Feb 12, 2015 at 8:17 PM, Tantilov, Emil S <emil.s.tanti...@intel.com
> wrote:
> >-----Original Message-----
> >From: Yotam Rubin [mailto:yo...@weka.io]
> >Sent: Thursday, February 12, 2015 4:48 AM
> >To: e1000-devel@lists.sourceforge.net
> >Subject: [E1000-devel] Enabling Loopback TX by default for all VFs
> >
> >Hey,
> >
> >The 82599 and x540 support loopback tx traffic for VF's through the
> >PFVMTXSW registers. The current driver doesn't enable this functionality.
> >Is there a reason why we shouldn't enable loopback traffic by default?
>
> If you set it then the VM will receive its own traffic (Tx is looped
> back). I don't think this is something most users would want, not to
> mention it may impact performance. You can enable it for debugging I
> suppose, but enabling it by default does not seem like a good idea.
>
> Is there a reason you want to loop the transmitted traffic back to the VF?
>
> Thanks,
> Emil
>
> >Thanks,
> > Yotam
>
------------------------------------------------------------------------------
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