[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200908180656.54011.vda.linux@googlemail.com>
Date: Tue, 18 Aug 2009 06:56:53 +0200
From: Denys Vlasenko <vda.linux@...glemail.com>
To: David Miller <davem@...emloft.net>
Cc: tim.bird@...sony.com, r.schwebel@...gutronix.de,
linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org,
arjan@...ux.intel.com, kernel@...gutronix.de,
netdev@...r.kernel.org
Subject: Re: new ipdelay= option for faster netboot
On Tuesday 18 August 2009 03:27, David Miller wrote:
> From: Tim Bird <tim.bird@...sony.com>
> Date: Mon, 17 Aug 2009 18:24:26 -0700
>
> > David Miller wrote:
> >> I have card/switch combinations that take up to 10 seconds to
> >> negotiate a proper link.
> >
> > What types of delays are these timeouts supposed to
> > cover?
>
> The problem is that if you don't first give at least some time for the
> link to come up, the remaining time it takes the link to come up will
> end up chewing into the actual bootp/dhcp protocol timeouts. And
> that's what we're trying to avoid.
But in this case, they assign a static IP. They do not use DHCP.
So they pay this time penalty even if they wouldn't use networking
until sometime later (or never).
Since DHCP and any other networking activity like TCP connects
accomodate packet loss, things should work even without any delay
in kernel IP config code. The delay will be just shifted to the
moment when first DHCP/TCP/whatever negotiation happens.
If dropping delays altogether sounds too big a change,
then it makes sense at least to allow people to tweak it with
ipdelay=TIME_IN_MS
--
vda
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists