On Sunday 27 November 2005 02:23, you wrote: > Michael Frank wrote: > >>>The adjusted timeout mechanism polls the carrier every > >>>100ms and polls for a good carrier for N_CARRIER_POLL > >>>(3) _consecutive_ cycles or 10s maximum. > >> > >>Why do you increase the maximum again? > > > > In the _current_ implementation, the timeout is > > effectively a fixed delay as the carrier for most > > NIC's is very fast and "not to be trusted" > > > > In _this_ implementation this is a true timeout which > > will only be reached in case of NIC failure. > > > > To clarify the practical delay of this implementation > > N_CARRIER_POLL * 0.1s + a few 100 to few 1000 us > > , 0.3s - 10 times as fast as current implementation ;) > > I understand that, but my sis900 for example does support > netpoll but it doesn't detect a carrier for some reason > I haven't debugged yet, which means I have to wait for > 10s again.
I suppose we should have an extra optional parameter to adjust N_CARRIER_POLL? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
