From: Erwan Velu <erwanaliasr1@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Remarks and comments about ipconfig behavior
Date: Sat, 15 Sep 2012 18:18:24 +0200 [thread overview]
Message-ID: <5054AA50.70108@gmail.com> (raw)
In-Reply-To: <20120913.163134.361379133013906511.davem@davemloft.net>
Le 13/09/2012 22:31, David Miller a écrit :
> I've seen PHY/switch/hub combinations that take longer than 30 seconds to fully negotiate the link. There is really no upper limit to the link speed/duplex/etc. negoatiation process. Even if the actual negoatiation protocol had an upper limit on negoatiation time, hardware implementations do things like try sampling the quality of the cable signal and may choose to down-rev the advertised features and restart the negoatiation.
I do understand that some might need some longer values while some others like me really need a smaller one.
On my case, this 2mn wait breaks an hardware watchdog, so I did a small patch on my local build to get it reduced as I know the selected value works fine for this hardware setup. And it works now perfectly.
So could it be valuable to export it as a CONFIG_something instead of patching this #define ?
Cheers,
prev parent reply other threads:[~2012-09-15 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 20:21 Remarks and comments about ipconfig behavior Erwan Velu
2012-09-13 20:31 ` David Miller
2012-09-13 20:37 ` Erwan Velu
2012-09-13 20:45 ` David Miller
2012-09-13 21:59 ` [PATCH] ipconfig: Inform user if carrier is not ready Erwan Velu
2012-09-14 5:36 ` Francois Romieu
[not found] ` <50525C5D.8040302@hp.com>
2012-09-14 19:08 ` [PATCH V2] " Erwan Velu
2012-09-14 19:17 ` David Miller
2012-09-14 19:30 ` [PATCH V3] " Erwan Velu
2012-09-14 19:42 ` David Miller
2012-09-14 20:13 ` Erwan Velu
2012-09-14 20:23 ` David Miller
2012-09-14 20:59 ` Erwan Velu
2012-09-14 19:31 ` [PATCH V2] " Erwan Velu
2012-09-14 19:19 ` Rick Jones
2012-09-15 16:18 ` Erwan Velu [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=5054AA50.70108@gmail.com \
--to=erwanaliasr1@gmail.com \
--cc=davem@davemloft.net \
--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).