[Top] [All Lists]

Re: [PATCH 1/7] netpoll: shorten carrier detect timeout

To: Matt Mackall <mpm@xxxxxxxxxxx>
Subject: Re: [PATCH 1/7] netpoll: shorten carrier detect timeout
From: Patrick McHardy <kaber@xxxxxxxxx>
Date: Fri, 11 Mar 2005 05:35:05 +0100
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>, netdev@xxxxxxxxxxx, Jeff Moyer <jmoyer@xxxxxxxxxx>
In-reply-to: <20050310230117.GP3120@xxxxxxxxx>
References: <2.454130102@xxxxxxxxxxx> <422A4A38.4040303@xxxxxxxxx> <20050306002015.GD3120@xxxxxxxxx> <422A564D.4080809@xxxxxxxxx> <20050310230117.GP3120@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20050106 Debian/1.7.5-1
Matt Mackall wrote:
Ok, on closer inspection, the current logic is: the NIC reports
carrier detect nearly instaneously and thus its carrier detect
reporting is considered unreliable. Rather than immediately sending
packets, we wait for some interval for it to really be up so that the
backlog of console messages doesn't get pumped into the bit bucket.

So I'm going to change it from "flaky" to "untrustworthy" and add a

Why don't you trust an instaneously available carrier? Any
reason to assume there will be false positives?


<Prev in Thread] Current Thread [Next in Thread>