Re: new ipdelay= option for faster netboot

Tim Bird wrote:

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.

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

When you plug an ethernet cable in, you may have noticed it takes a
short time before the signal light comes on.  That's negotiation time.
Some are slower than others, but none of them do it instantly.

Is this something to do with power propagation to the
physical wire?

Not really.

Is there some MAC layer negotiation between the card and the switch?
Is it the time for the switch to do speed detection?

Yes and yes.

And, can any of this be more accurately determined
or guessed-at with knowledge of the onboard hardware?
Or is it dependent on external conditions?

It can be accurately determined with most cards (all modern ones)
because you get a notification when it's done, or you can poll the card.

That's why on the desktop it's able to detect when you plug in an
ethernet cable and start DHCP as soon as link negotiation is complete.

So the right thing to do, as David Miller suggested too, isn't a fixed
timeout.  It should wait for link state UP and then start DHCP
immediately.

-- Jamie