From: Rick Jones <rick.jones2@hpe.com>
To: David Miller <davem@davemloft.net>, nikolay@cumulusnetworks.com
Cc: jiri@resnulli.us, mst@redhat.com, gospo@cumulusnetworks.com,
virtualization@lists.linux-foundation.org,
bjornar.ness@gmail.com, vfalico@gmail.com,
netdev@vger.kernel.org, jay.vosburgh@canonical.com
Subject: Re: bonding (IEEE 802.3ad) not working with qemu/virtio
Date: Mon, 1 Feb 2016 10:49:54 -0800 [thread overview]
Message-ID: <56AFA8D2.50500@hpe.com> (raw)
In-Reply-To: <20160129.225924.1343743091073159760.davem@davemloft.net>
On 01/29/2016 10:59 PM, David Miller wrote:
> There should be a default speed/duplex setting for such devices as well.
> We can pick one that will be use universally for these kinds of devices.
There is at least one monitoring tool - collectl - which gets a trifle
upset when the actual speed through an interface is significantly
greater than the reported link speed. I have to wonder how unique it is
in that regard.
Doesn't mean there can't be a default, but does suggest it should be
rather high.
rick jones
next prev parent reply other threads:[~2016-02-01 18:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 16:24 bonding (IEEE 802.3ad) not working with qemu/virtio Bjørnar Ness
2016-01-28 13:33 ` Jiri Pirko
2016-01-28 13:53 ` Nikolay Aleksandrov
2016-01-28 14:10 ` Nikolay Aleksandrov
2016-01-29 21:31 ` Nikolay Aleksandrov
2016-01-29 21:45 ` Jay Vosburgh
2016-01-29 21:48 ` Nikolay Aleksandrov
2016-01-30 6:59 ` David Miller
2016-01-30 11:34 ` Jiri Pirko
2016-01-30 11:41 ` Nikolay Aleksandrov
2016-01-31 14:50 ` Michael S. Tsirkin
2016-02-01 18:49 ` Rick Jones [this message]
2016-01-31 14:58 ` Michael S. Tsirkin
2016-01-31 14:35 ` 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=56AFA8D2.50500@hpe.com \
--to=rick.jones2@hpe.com \
--cc=bjornar.ness@gmail.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=vfalico@gmail.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;
as well as URLs for NNTP newsgroup(s).