From: Francois Romieu <romieu@fr.zoreil.com>
To: hayeswang <hayeswang@realtek.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bowgotsai@google.com, "'Ryankao'" <ryankao@realtek.com>
Subject: Re: r8169 auto speed down issue
Date: Sat, 30 Mar 2013 13:42:56 +0100 [thread overview]
Message-ID: <20130330124256.GA19236@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <555174DCA0B0431BB3AE9CCD464E5896@realtek.com.tw>
hayeswang <hayeswang@realtek.com> :
[...]
> Sorry for my unclear descriptor. I just think a case that the nic suspends or
> shutdowns without cable plugging. Then, the cable is plugged again. If the nic
> speed down to 10M and the link partner force 100M, the issue appears again. If
> the nic doesn't speed down for normal link partner, it requires more power
> when the linking recovers.
Yes. The nic can not guess what the user values most: power saving in a
stable link layer configuration vs ability to detect and adapt to a yet
unseen configuration.
It could be a reason why EEE exists.
> Finally, I determine to set the speed to 10M when the link partner supports
> 10M. And for the other case, setting the speed to 100M. This avoids the giga
> nic to keep the speed to 1000M, and could fix this issue.
> However, I wonder if there is a switch which forces the speed to giga.
We can check if the partner supports 100M too. It's almost free and it will
avoid this problem.
--
Ueimor
prev parent reply other threads:[~2013-03-30 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EECA12DD88643FD9006350514D96C8E@realtek.com.tw>
2013-03-28 23:19 ` r8169 auto speed down issue Francois Romieu
2013-03-29 2:11 ` hayeswang
2013-03-29 7:20 ` Francois Romieu
2013-03-29 8:20 ` hayeswang
2013-03-30 12:42 ` Francois Romieu [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=20130330124256.GA19236@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=bowgotsai@google.com \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ryankao@realtek.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