From: Arnd Bergmann <arnd@arndb.de>
To: Benny Amorsen <benny+usenet@amorsen.dk>
Cc: "Fischer\, Anna" <anna.fischer@hp.com>,
Yaron Haviv <yaronh@voltaire.com>,
evb@yahoogroups.com, shemminger@linux-foundation.org,
davem@davemloft.net, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, adobriyan@gmail.com,
"Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>,
virtualization@lists.linux-foundation.org
Subject: Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Sat, 8 Aug 2009 11:44:39 +0200 [thread overview]
Message-ID: <200908081144.39501.arnd@arndb.de> (raw)
In-Reply-To: <m3d476hepp.fsf@ursa.amorsen.dk>
On Saturday 08 August 2009, Benny Amorsen wrote:
> Would a SRIOV NIC with VEPA support show up as multiple devices? I.e.
> would I get e.g. eth0-eth7 for a NIC with support for 8 virtual
> interfaces? Would they have different MAC addresses?
It could, but the idea of SR-IOV is that it shows up as 8 PCI
devices. One of them is owned by the host and is seen as eth0
there. The other seven PCI devices (virtual functions) are meant
to be assigned to the guest using PCI passthrough and will show
up as the guests eth0, each one with its own MAC address.
An other mode of operation is VMDq, where the host owns all
interfaces and you might see eth0-eth7 there. You can then attach
a qemu process with a raw packet socket or a single macvtap port
for each of those interfaces. This is not yet implemented in Linux,
so how it will be done is still open. It might all be integrated
into macvlan or some new subsystem alternatively.
AFAIK, every SR-IOV adapter can also be operated as a VMDq adapter,
but there are VMDq adapters that do not support SR-IOV.
Arnd <><
next prev parent reply other threads:[~2009-08-08 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:35 [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support Yaron Haviv
2009-08-07 21:00 ` Fischer, Anna
2009-08-08 9:22 ` Arnd Bergmann
2009-08-07 21:06 ` Paul Congdon (UC Davis)
2009-08-07 21:36 ` Stephen Hemminger
2009-08-09 11:19 ` Or Gerlitz
2009-08-10 15:20 ` Stephen Hemminger
2009-08-10 15:28 ` Arnd Bergmann
2009-08-10 16:32 ` Fischer, Anna
2009-08-10 16:51 ` Stephen Hemminger
2009-08-10 19:18 ` Arnd Bergmann
2009-08-27 12:35 ` Or Gerlitz
[not found] ` <0199E0D51A61344794750DC57738F58E6D6A6CD803__29862.6656564467$1249679159$gmane$org@GVW1118EXC.americas.hpqcorp.net>
2009-08-08 8:50 ` Benny Amorsen
2009-08-08 9:44 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 17:33 Fischer, Anna
2009-08-07 4:00 ` Stephen Hemminger
2009-08-07 11:29 ` Arnd Bergmann
2009-08-07 19:44 ` [evb] " Paul Congdon (UC Davis)
2009-08-10 15:23 ` Arnd Bergmann
2009-08-10 15:59 ` Fischer, Anna
2009-08-10 16:16 ` Arnd Bergmann
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=200908081144.39501.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=adobriyan@gmail.com \
--cc=anna.fischer@hp.com \
--cc=benny+usenet@amorsen.dk \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=evb@yahoogroups.com \
--cc=netdev@vger.kernel.org \
--cc=ptcongdon@ucdavis.edu \
--cc=shemminger@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yaronh@voltaire.com \
/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).