From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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 19:37:37 +0300 [thread overview]
Message-ID: <20090812163737.GA29903@redhat.com> (raw)
In-Reply-To: <4A82EA37.3010902@gmail.com>
On Wed, Aug 12, 2009 at 12:13:43PM -0400, Gregory Haskins wrote:
> Michael S. Tsirkin wrote:
> > On Wed, Aug 12, 2009 at 09:51:45AM -0400, Gregory Haskins wrote:
> >> 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 <><
> >> Yeah, this would be the config I would be interested in.
> >
> > Hmm, this wouldn't be the config to use for the benchmark though: there
> > are just too many variables. If you want both guest to guest and guest
> > to host, create 2 nics in the guest.
> >
> > Here's one way to do this:
> >
> > -net nic,model=virtio,vlan=0 -net user,vlan=0
> > -net nic,vlan=1,model=virtio,vhost=veth0
> > -redir tcp:8022::22
> >
> > -net nic,model=virtio,vlan=0 -net user,vlan=0
> > -net nic,vlan=1,model=virtio,vhost=veth1
> > -redir tcp:8023::22
> >
> > In guests, for simplicity, configure eth1 and eth0
> > to use separate subnets.
>
> I can try to do a few variations, but what I am interested is in
> performance in a real-world L2 configuration. This would generally mean
> all hosts (virtual or physical) in the same L2 domain.
>
> If I get a chance, though, I will try to also wire them up in isolation
> as another data point.
>
> Regards,
> -Greg
>
>
Or patch macvlan to support guest to guest:
http://markmail.org/message/sjy74g57qsvdo2wh
That patch needs to be updated to support guest to guest multiast,
but it seems functional enough for your purposes.
--
MST
--
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 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 21:27 Michael S. Tsirkin
2009-08-11 23:49 ` Gregory Haskins
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 11:56 ` Gregory Haskins
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 13:06 ` Michael S. Tsirkin
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:51 ` Gregory Haskins
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 16:13 ` Gregory Haskins
2009-08-12 16:37 ` Michael S. Tsirkin [this message]
2009-08-12 13:04 ` 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=20090812163737.GA29903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox