From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Fischer, Anna" <anna.fischer@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: L2 switching in igb
Date: Thu, 10 Sep 2009 10:30:09 -0700 [thread overview]
Message-ID: <4AA937A1.9070504@intel.com> (raw)
In-Reply-To: <4AA8B317.2080706@voltaire.com>
Or Gerlitz wrote:
> Note that VEPA mode is a characteristic of the PF, correct? and the PF
> resides in the host kernel. Also, as I wrote you earlier, I do see many
> schemes where a VF spawned in the host kernel IS very useful, and as
> such I'd be happy to continue the discussion on the approach suggested
> by Dave and Stephen, can you provide a pointer? (thanks).
>
> Or.
You are correct, the vSwitch can basically do VEPA by disabling local
loopback enable bit in the DTXSWC register. This would force all
traffic from the PF/VFs out the lan physical port and from the lan
physical port to the appropriate PF/VFs without doing any switching in
between PF/VFs.
I am currently thinking what probably needs to be done is to add an
rtnl_link_ops interface to handle vSwitch configuration that could then
be applied to the igb netdevs that support VEPA/vSwitch technologies. A
subset of that interface could then be dedicated to VF configuration to
handle things such as spawning VFs, setting the default mac addresses,
security controls, etc.
Thanks,
Alex
next prev parent reply other threads:[~2009-09-10 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 9:16 L2 switching in igb Or Gerlitz
2009-09-04 4:35 ` Alexander Duyck
2009-09-10 8:04 ` Or Gerlitz
2009-09-10 17:30 ` Alexander Duyck [this message]
2009-09-14 10:02 ` Or Gerlitz
2009-09-15 2:52 ` Alexander Duyck
2009-09-15 13:19 ` Or Gerlitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA937A1.9070504@intel.com \
--to=alexander.h.duyck@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=anna.fischer@hp.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).