From: "James Harper" <james.harper@bendigoit.com.au>
To: "Pasi Kärkkäinen" <pasik@iki.fi>, "Pavel Mat??ja" <pavel@netsafe.cz>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen-netfront: report link speed to ethtool
Date: Sat, 19 Nov 2011 12:13:29 +1100 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01EDFD5F@trantor> (raw)
In-Reply-To: <20111118193712.GQ12984@reaktio.net>
> The reported NIC speed in the VM does not mean anything really, because
> it's all virtual "hardware", and the reported speed is not any kind of limit.
>
> Even if windows VM says it's 10 Mbit/sec NIC you can still talk as fast as your
> system can go.
>
That's not quite true. Windows or some application might equate 10Mbit == WAN and do things a bit differently. BITS certainly scales back throughput but I think it does that based on actual tested throughput, although it might use the link speed as an indication.
A HVM domain needs to report something because it is emulated hardware. A way to pass that through from Dom0 would be nice, but probably a lot of work for little gain vs just making up a reasonable figure.
James
next prev parent reply other threads:[~2011-11-19 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 16:48 [PATCH] xen-netfront: report link speed to ethtool Olaf Hering
2011-11-18 17:46 ` Ben Hutchings
2011-11-18 18:43 ` Olaf Hering
2011-11-18 19:10 ` Ben Hutchings
2011-11-18 19:17 ` Olaf Hering
2011-11-18 18:44 ` Rick Jones
2011-11-18 18:46 ` Jeremy Fitzhardinge
2011-11-18 18:58 ` use a special value of -2 for virtual devices to report indeterminate speed? Rick Jones
2011-11-18 19:13 ` Ben Hutchings
2011-11-18 19:11 ` [PATCH] xen-netfront: report link speed to ethtool Pavel Matěja
2011-11-18 19:37 ` Pasi Kärkkäinen
2011-11-19 1:13 ` James Harper [this message]
2011-11-19 1:32 ` James Harper
2011-11-18 19:11 ` David Miller
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=AEC6C66638C05B468B556EA548C1A77D01EDFD5F@trantor \
--to=james.harper@bendigoit.com.au \
--cc=pasik@iki.fi \
--cc=pavel@netsafe.cz \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).