From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: Simon Arlott <3d1f88d2534993eb311hc0vm0003uvpw@thunder.lp0.eu>
Subject: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
Date: Wed, 31 Jan 2007 15:27:36 +0100
User-Agent: KMail/1.9.6
Cc: linux-kernel@vger.kernel.org
References: <45BFB841.9030200@simon.arlott.org.uk>
In-Reply-To: <45BFB841.9030200@simon.arlott.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701311527.39343.duncan.sands@math.u-psud.fr>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1006
Lines: 21

> The device is only polled for status every 5 seconds yet status updates
> occur as often as every second - when the line is down the status changes
> between "down" and "attempting to activate" every 2 seconds.  

How much overhead does polling involve?  [A particularly problematic case
is when polling is failing - I've occasionally seen speedtouch modems
where polling fails every time (not sure why) and for some reason this
increases system load considerably, which is why the speedtch driver has
a dynamic polling interval].  If polling overhead is basically nothing,
then this change is OK with me.  Otherwise the next simplest thing to do
is to have a short polling interval when the line is down, and a longer
one when the line is up.

Ciao,

Duncan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/