From: Gregory Haskins <gregory.haskins@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Michael S. Tsirkin" <mst@redhat.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 09:51:45 -0400 [thread overview]
Message-ID: <4A82C8F1.4030703@gmail.com> (raw)
In-Reply-To: <200908121540.44928.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
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.
Regards,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2009-08-12 13:51 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:41 ` Gregory Haskins
2009-08-12 12:41 ` Gregory Haskins
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 13:06 ` Michael S. Tsirkin
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 [this message]
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 12:52 ` Arnd Bergmann
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:05 ` Michael S. Tsirkin
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=4A82C8F1.4030703@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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=mst@redhat.com \
--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.