I've been asked to examine my driver to debounce link state change
messages. (Ultimately I'll do this for mac_update_link() too. When my
driver is ported to nemo.)
So the question is, for an 802.3 device (in this case its 10/100 only),
what guidelines are appropriate for debouncing link status changes?
I always assumed early/fast notification was good for the benefit of IP
multipathing and 802.3ad, but perhaps the link bounces that occur when
link is renegotiated due to administrative action are detrimental.
Certainly it seems like they don't help out with NWAM.
So, before I just go and "guess" at some values, I'd like to hear
thoughts as to guidelines for debouncing these link state changes.
Assume for the moment that my device can generate a link state change
interrupt. How long must I wait for link to settle before I "believe"
it? Should I poll more frequently than that? (E.g. poll every 1/10
sec, and wait for link to be stable for 1 second before sending a
notification?)
Thanks in advance for any suggestions on this.
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
