From: linux_kvm@proinbox.com
To: "KVM mailing list" <kvm@vger.kernel.org>
Subject: suggested vhost link speed settings
Date: Sat, 27 Nov 2010 21:26:08 -0500 [thread overview]
Message-ID: <1290911168.20434.1407472791@webmail.messagingengine.com> (raw)
Hi list,
Being that the virtio interfaces are stated as acheiving 5-8 Gb
throughput now with vhost, as opposed to 1Gb without, how should their
link speed be defined when the choices are 2500M or 10000M?
I have them plotted out to make a 10Gb bond out of a pair, counting on
5Gb max each, which I'm imagining can be acheived without concern based
on what I read.
If I set them to 'auto-negotiate' will it internally flap between &
cause undesirable consequences?
I don't want to set them at 2500 in case they ever do need to reach
closer to 5 each.
I'm not at a point where I can test anything yet, I'm just planning &
preconfiguring so far.
For the sake of preventing issues down the line I wanted to see if
there's a consensus or standard for this scenario and be as sure as
possible ahead of time.
Thanks,
-C
next reply other threads:[~2010-11-28 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 2:26 linux_kvm [this message]
2010-11-28 13:03 ` suggested vhost link speed settings Michael Tokarev
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=1290911168.20434.1407472791@webmail.messagingengine.com \
--to=linux_kvm@proinbox.com \
--cc=kvm@vger.kernel.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