[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090812134247.GA29340@redhat.com>
Date: Wed, 12 Aug 2009 16:42:47 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Gregory Haskins <gregory.haskins@...il.com>,
netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
hpa@...or.com, Patrick Mullaney <pmullaney@...ell.com>
Subject: Re: [PATCHv2 0/2] vhost: a kernel-level virtio server
On Wed, Aug 12, 2009 at 03:40:44PM +0200, Arnd Bergmann wrote:
> On Wednesday 12 August 2009, Michael S. Tsirkin wrote:
> > > 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
> > >
> > Heh, you don't need a bridge in this picture:
> >
> > guest 1 - vhost - veth0 - veth1 - vhost guest 2
>
> Sure, but the setup I described is the one that I would expect
> to see in practice because it gives you external connectivity.
>
> Measuring two guests communicating over a veth pair is
> interesting for finding the bottlenecks, but of little
> practical relevance.
>
> Arnd <><
Oh, hopefully macvlan will soon allow that.
--
MST
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists