From: Brian Jackson <brian@vten.us>
To: Stefan Bauer <stefan.bauer@cubewerk.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "sb@plzk.de" <sb@plzk.de>
Subject: Re: Nic Bonding - throughput for guest
Date: Fri, 24 Oct 2014 10:13 -0500 [thread overview]
Message-ID: <1829837.xfoWWHdfGz@iggy-ub> (raw)
In-Reply-To: <zarafa.544a4808.29b6.6c1654053d446772@srv1.localhost>
On Friday, October 24, 2014 02:37:28 PM Stefan Bauer wrote:
> Hi,
>
>
> please CC me - I'm not subscribed to this list.
>
>
> I'm looking forward to bond the 2 Nics from my KVM Host (2 x 1GbE) to
> increase throughput for my guest.
>
>
> Currently my guest has a e1000 nic attached.
That probably won't cut it. You'll want to go with virtio-net and vhost.
>
>
> Do i have to tune anything else so my kvm guest can operate with 2 x 1gbit
> (to different clients) ?
Nope. Just use a standard bridge. The reported speed in the guest really has
nothing to do with the actual achievable speed. I've seen close to 20gbit/sec
guest to host with virtio+vhost.
>
>
> I'm using 802.1d with hash_policy layer3+4 for bonding (this is tested and
> working with our switches).
Most network setups I've seen required pretty specific traffic patterns to
actually get >1gbit speed. i.e. you're unlikely to get >1gbit between 2 hosts.
You're going to need multiple hosts in the mix to get it to work.
>
>
> Kind Regards.
>
>
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-10-24 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:37 Nic Bonding - throughput for guest Stefan Bauer
2014-10-24 15:13 ` Brian Jackson [this message]
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=1829837.xfoWWHdfGz@iggy-ub \
--to=brian@vten.us \
--cc=kvm@vger.kernel.org \
--cc=sb@plzk.de \
--cc=stefan.bauer@cubewerk.de \
/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