From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
hpa@zytor.com, Patrick Mullaney <pmullaney@novell.com>
Subject: Re: [PATCHv2 0/2] vhost: a kernel-level virtio server
Date: Wed, 12 Aug 2009 16:06:12 +0300 [thread overview]
Message-ID: <20090812130612.GC29200@redhat.com> (raw)
In-Reply-To: <200908121452.01802.arnd@arndb.de>
On Wed, Aug 12, 2009 at 02:52:01PM +0200, Arnd Bergmann wrote:
> On Wednesday 12 August 2009, Gregory Haskins wrote:
> > >> Are you saying SRIOV is a requirement, and I can either program the
> > >> SRIOV adapter with a mac or use promis? Or are you saying I can use
> > >> SRIOV+programmed mac OR a regular nic + promisc (with a perf penalty).
> > >
> > > SRIOV is not a requirement. And you can also use a dedicated
> > > nic+programmed mac if you are so inclined.
> >
> > Makes sense. Got it.
> >
> > I was going to add guest-to-guest to the test matrix, but I assume that
> > is not supported with vhost unless you have something like a VEPA
> > enabled bridge?
> >
>
> If I understand it correctly, you can at least connect a veth pair
> to a bridge, right? Something like
>
> veth0 - veth1 - vhost - guest 1
> eth0 - br0-|
> veth2 - veth3 - vhost - guest 2
>
> It's a bit more complicated than it need to be, but should work fine.
>
> Arnd <><
Heh, you don't need a bridge in this picture:
guest 1 - vhost - veth0 - veth1 - vhost guest 2
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
hpa@zytor.com, Patrick Mullaney <pmullaney@novell.com>
Subject: Re: [PATCHv2 0/2] vhost: a kernel-level virtio server
Date: Wed, 12 Aug 2009 16:06:12 +0300 [thread overview]
Message-ID: <20090812130612.GC29200@redhat.com> (raw)
In-Reply-To: <200908121452.01802.arnd@arndb.de>
On Wed, Aug 12, 2009 at 02:52:01PM +0200, Arnd Bergmann wrote:
> On Wednesday 12 August 2009, Gregory Haskins wrote:
> > >> Are you saying SRIOV is a requirement, and I can either program the
> > >> SRIOV adapter with a mac or use promis? Or are you saying I can use
> > >> SRIOV+programmed mac OR a regular nic + promisc (with a perf penalty).
> > >
> > > SRIOV is not a requirement. And you can also use a dedicated
> > > nic+programmed mac if you are so inclined.
> >
> > Makes sense. Got it.
> >
> > I was going to add guest-to-guest to the test matrix, but I assume that
> > is not supported with vhost unless you have something like a VEPA
> > enabled bridge?
> >
>
> If I understand it correctly, you can at least connect a veth pair
> to a bridge, right? Something like
>
> veth0 - veth1 - vhost - guest 1
> eth0 - br0-|
> veth2 - veth3 - vhost - guest 2
>
> It's a bit more complicated than it need to be, but should work fine.
>
> Arnd <><
Heh, you don't need a bridge in this picture:
guest 1 - vhost - veth0 - veth1 - vhost guest 2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-12 13:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 21:27 [PATCHv2 0/2] vhost: a kernel-level virtio server Michael S. Tsirkin
2009-08-11 21:27 ` Michael S. Tsirkin
2009-08-11 21:27 ` Michael S. Tsirkin
2009-08-11 23:49 ` Gregory Haskins
2009-08-11 23:49 ` Gregory Haskins
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 11:56 ` Gregory Haskins
2009-08-12 11:56 ` Gregory Haskins
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 12:41 ` Gregory Haskins
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 13:06 ` Michael S. Tsirkin [this message]
2009-08-12 13:06 ` Michael S. Tsirkin
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:51 ` Gregory Haskins
2009-08-12 13:51 ` Gregory Haskins
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 16:13 ` Gregory Haskins
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:13 ` Gregory Haskins
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:06 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 12:41 ` Gregory Haskins
2009-08-12 7:16 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-08-11 21:27 Michael S. Tsirkin
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=20090812130612.GC29200@redhat.com \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregory.haskins@gmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=pmullaney@novell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.