From: Helmut Grohne <h.grohne@cygnusnetworks.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Rick Jones <rick.jones2@hp.com>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Max Krasnyansky <maxk@qti.qualcomm.com>
Subject: Re: TUN/TAP: tap driver reports bogus interface speed in ethtool operations
Date: Tue, 23 Jul 2013 18:03:54 +0200 [thread overview]
Message-ID: <27AF15CB-BF6D-4C28-B9C1-BF880C482D12@cygnusnetworks.de> (raw)
In-Reply-To: <20130723085611.0c77c314@nehalam.linuxnetplumber.net>
On 23.07.2013, at 17:56, Stephen Hemminger <stephen@networkplumber.org> wrote:
> I have hack patch to allow overwriting speed, info, and statistics that is part
> of how we use TUN as dummy devices. How far do you think makes sense?
That could prove useful for creating test environments for tools, that use ethtool.
If you have a better patch, then go for it. The reason for why I did not include
other settings was that I don't need them. I'm open to other solutions as well, as
long as they either make the speed modifiable or something faster than SPEED_10.
Helmut
next prev parent reply other threads:[~2013-07-23 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2F174B03-5074-4BA0-B91A-8F2F62C2B082@cygnusnetworks.de>
[not found] ` <5192BDD6.6060703@qti.qualcomm.com>
[not found] ` <3E916AF0-C587-443D-B653-C968A96C8751@cygnusnetworks.de>
[not found] ` <48A2F278-A32C-47C6-AD2D-1FC15EC73B88@cygnusnetworks.de>
[not found] ` <51E5BE27.3060207@qti.qualcomm.com>
2013-07-23 13:32 ` TUN/TAP: tap driver reports bogus interface speed in ethtool operations Helmut Grohne
2013-07-23 15:49 ` Rick Jones
2013-07-23 15:56 ` Stephen Hemminger
2013-07-23 16:03 ` Helmut Grohne [this message]
2013-07-23 17:28 ` [RFC 1/2] tun: allow overrriding ethtool info Stephen Hemminger
2013-07-23 17:29 ` [RFC 2/2] tun: allow overriding statistics Stephen Hemminger
2013-07-23 19:04 ` TUN/TAP: tap driver reports bogus interface speed in ethtool operations Ben Hutchings
2013-07-30 6:20 ` Helmut Grohne
2013-07-30 10:51 ` Ben Hutchings
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=27AF15CB-BF6D-4C28-B9C1-BF880C482D12@cygnusnetworks.de \
--to=h.grohne@cygnusnetworks.de \
--cc=davem@davemloft.net \
--cc=maxk@qti.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=stephen@networkplumber.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).