Re: new ipdelay= option for faster netboot

From: Tim Bird <redacted>
Date: Mon, 17 Aug 2009 18:40:48 -0700

David Miller wrote:

quoted

From: Tim Bird <redacted>
Date: Mon, 17 Aug 2009 18:24:26 -0700

quoted

David Miller wrote:

quoted

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.

What link?  I'm not that familiar with networking.

The speed and duplex settings which are negotiated or forced between
the ethernet card and whatever is at the other end of the cable.

Assuming I'm using ethernet, what link needs to come up?

All modern ethernet cards do autonegotiation of link parameters
with whatever is at the other end of the ethernet cable.  Cards
created ages ago which only support 10MB half-duplex typically
do not support autonegotiation at all.

This autonegotiation works like a protocol where the two link partners
go back and forth trying to figure out the best speed and duplex
settings to use.  There are advertisements of link capabilities and
stuff like that.

It should happen almost instantaneously, but there are millions
upon millions of cruddy parts out there, and some of them take
a long time to go through this negotiation process.