virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: qemu-devel@nongnu.org
Cc: "Fischer, Anna" <anna.fischer@hp.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: [Qemu-devel] Re: Guest bridge setup variations
Date: Thu, 10 Dec 2009 20:20:26 +0000	[thread overview]
Message-ID: <200912102020.26724.arnd@arndb.de> (raw)
In-Reply-To: <784CAF36-3F28-4FFD-82A2-0A4E54EDB831@suse.de>

On Thursday 10 December 2009 19:14:28 Alexander Graf wrote:
> > This is something I also have been thinking about, but it is not what
> > I was referring to above. I think it would be good to keep the three
> > cases (macvlan, VMDq, SR-IOV) as similar as possible from the user
> > perspective, so using macvlan as an infrastructure for all of them
> > sounds reasonable to me.
> 
> Oh, so you'd basically do -net vt-d,if=eth0 and the rest would
> automatically work? That's a pretty slick idea!

I was only referring to how they get set up under the covers, e.g.
creating the virtual device, configuring the MAC address etc, not
the qemu side, but that would probably make sense as well.

Or even better, qemu should probably not even know the difference
between macvlan and VT-d. In both cases, it would open a macvtap
file, but for VT-d adapters, the macvlan infrastructure can
use hardware support, much in the way that VLAN tagging gets
offloaded automatically to the hardware.

	Arnd <><

  reply	other threads:[~2009-12-10 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 16:07 Guest bridge setup variations Arnd Bergmann
2009-12-09 19:36 ` [Qemu-devel] " Anthony Liguori
2009-12-10  9:19   ` Arnd Bergmann
2009-12-10 23:53     ` Anthony Liguori
2009-12-14 12:09       ` Arnd Bergmann
2009-12-10 12:26 ` Fischer, Anna
2009-12-10 14:18   ` Arnd Bergmann
2009-12-10 19:14     ` Alexander Graf
2009-12-10 20:20       ` Arnd Bergmann [this message]
2009-12-10 20:37         ` [Qemu-devel] " Alexander Graf

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=200912102020.26724.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=anna.fischer@hp.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtualization@lists.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).