From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: [PATCH 1/8] e1000e: cleanup several stats issues
Date: Mon, 28 Apr 2008 15:13:22 -0700 [thread overview]
Message-ID: <48164C02.9060902@intel.com> (raw)
In-Reply-To: <481173B9.3010006@garzik.org>
Jeff Garzik wrote:
> Auke Kok wrote:
>> From: Bruce Allan <bruce.w.allan@intel.com>
>>
>> Several stats registers are completely unused and we just waste pci
>> bus time reading them. We also omit using the high 32 bits of the GORC/
>> GOTC counters. We can just read clear them and only read the low
>> registers.
>>
>> Mii-tool can also break es2lan if it executes a MII PHY register
>> ioctl while the device is in autonegotiation. Unfortunately it seems
>> that several applications and installations still perform this ioctl
>> call periodically and especially in this crucial startup time. We
>> can fool the ioctl by providing fail safe information that mimics
>> the "down" link state and only perform the dangerous PHY reads once
>> after link comes up to fill in the real values. As long as link
>> stays up the information will not change.
>>
>> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
>> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
>
> applied 1-8
>
> I was mainly waiting for the discussion of the abuse of the ethtool
> interface, which I chose to allow.
>
> Now, send me a patch to the ethtool man page for this new behavior :)
it almost seems more appropriate to send a patch to the e1000 README and explain
the parameter use in there since this is a per-driver modification and there's
nothing special about the ethtool call itself.
Would you be OK with a general patch to ethtool that states that "drivers may
interpret values differently and users should consult the driver's source code or
README for proper use of the parameter." ?
This seems the logical solution.
Auke
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-28 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 18:09 [PATCH 1/8] e1000e: cleanup several stats issues Auke Kok
2008-04-23 18:09 ` [PATCH 2/8] e1000e: Add interrupt moderation run-time ethtool interface Auke Kok
2008-04-23 18:09 ` [PATCH 3/8] e1000e: Fix HW Error on es2lan, ARP capture issue by BMC Auke Kok
2008-04-23 18:09 ` [PATCH 4/8] e1000e: lower ring minimum size to 64 Auke Kok
2008-04-23 18:12 ` [E1000-devel] " Kok, Auke
2008-04-23 18:09 ` [PATCH 5/8] ixgbe: save and restore pcie/msi state to support EEH recovery Auke Kok
2008-04-23 18:09 ` [PATCH 6/8] e1000e: " Auke Kok
2008-04-23 18:09 ` [PATCH 7/8] [RESEND] igb: " Auke Kok
2008-04-23 18:09 ` [PATCH 8/8] e1000e: Increment version to 0.2.1 Auke Kok
2008-04-25 6:01 ` [PATCH 1/8] e1000e: cleanup several stats issues Jeff Garzik
2008-04-25 16:39 ` Kok, Auke
2008-04-28 22:13 ` Kok, Auke [this message]
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=48164C02.9060902@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).