netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Amorsen <benny+usenet@amorsen.dk>
To: "Fischer\, Anna" <anna.fischer@hp.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	Yaron Haviv <yaronh@voltaire.com>,
	"bridge@lists.linux-foundation.org"
	<bridge@lists.linux-foundation.org>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"adobriyan@gmail.com" <adobriyan@gmail.com>,
	"Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"evb@yahoogroups.com" <evb@yahoogroups.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Sat, 08 Aug 2009 10:50:10 +0200	[thread overview]
Message-ID: <m3d476hepp.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E6D6A6CD803__29862.6656564467$1249679159$gmane$org@GVW1118EXC.americas.hpqcorp.net> (Anna Fischer's message of "Fri\, 7 Aug 2009 21\:00\:54 +0000")

"Fischer, Anna" <anna.fischer@hp.com> writes:

> If you do have a SRIOV NIC that supports VEPA, then I would think that
> you do not have QEMU or macvtap in the setup any more though. Simply
> because in that case the VM can directly access the VF on the physical
> device. That would be ideal.

I'm just trying to understand how this all works, so I'm probably asking
a stupid question:

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?


/Benny

  parent reply	other threads:[~2009-08-08  8:50 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 [this message]
2009-08-08  9:44     ` Arnd Bergmann
  -- 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=m3d476hepp.fsf@ursa.amorsen.dk \
    --to=benny+usenet@amorsen.dk \
    --cc=adobriyan@gmail.com \
    --cc=anna.fischer@hp.com \
    --cc=arnd@arndb.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=evb@yahoogroups.com \
    --cc=netdev@vger.kernel.org \
    --cc=ptcongdon@ucdavis.edu \
    --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).