From: Rick Jones <rick.jones2@hp.com>
To: Francois Romieu <romieu@fr.zoreil.com>,
Zhu Yanjun <Yanjun.Zhu@windriver.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
viro@zeniv.linux.org.uk, davem@davemloft.net,
sergei.shtylyov@cogentembedded.com, jonathon.reinhart@gmail.com
Subject: Re: [PATCH 1/1] tun: change speed from 10M to dynamically configured
Date: Fri, 13 Feb 2015 13:32:23 -0800 [thread overview]
Message-ID: <54DE6D67.5000601@hp.com> (raw)
In-Reply-To: <20150213212830.GA29912@electric-eye.fr.zoreil.com>
It is perhaps as much a bug in the monitoring tools as anything else,
but I have come across (versions of) software - such as collectl I think
- which when presented with counters indicating a data rate higher than
the reported link rate of the interface get somewhat cranky.
rick jones
next prev parent reply other threads:[~2015-02-13 21:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 6:19 [PATCH V3 0/1] tun: dynamically set speed of tun Zhu Yanjun
2015-02-13 6:19 ` [PATCH 1/1] tun: change speed from 10M to dynamically configured Zhu Yanjun
2015-02-13 10:03 ` yzhu1
2015-02-13 10:45 ` Sergei Shtylyov
2015-02-13 21:28 ` Francois Romieu
2015-02-13 21:32 ` Rick Jones [this message]
2015-02-13 23:15 ` Francois Romieu
2015-02-16 2:31 ` yzhu1
2015-02-16 17:03 ` Stephen Hemminger
2015-02-18 19:29 ` Andy Gospodarek
2015-02-18 19:39 ` Andy Gospodarek
2015-02-19 20:37 ` David Miller
2015-02-19 20:40 ` David Miller
2015-02-20 0:41 ` Simon Horman
2015-02-20 2:35 ` Andy Gospodarek
2015-02-20 20:07 ` David Miller
2015-02-21 3:07 ` Andy Gospodarek
2015-02-20 10:01 ` David Laight
2015-02-19 20:56 ` roopa
-- strict thread matches above, loose matches on Subject: below --
2015-02-12 5:35 [PATCH 0/1] tun: dynamically set speed of tun Zhu Yanjun
2015-02-12 5:35 ` [PATCH 1/1] tun: change speed from 10M to dynamically configured Zhu Yanjun
2015-02-12 12:55 ` Stephen Hemminger
2015-02-13 2:45 ` yzhu1
2015-02-13 3:25 ` Fan Du
2015-02-13 3:34 ` yzhu1
2015-02-12 13:52 ` Sergei Shtylyov
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=54DE6D67.5000601@hp.com \
--to=rick.jones2@hp.com \
--cc=Yanjun.Zhu@windriver.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jonathon.reinhart@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=viro@zeniv.linux.org.uk \
/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).