linux-kernel - Re: [PATCH 2/3] cxacru: Poll for device status more frequently.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45C0D602.70708@simon.arlott.org.uk>
Date:	Wed, 31 Jan 2007 17:46:42 +0000
From:	Simon Arlott <simon@...ott.org>
To:	Duncan Sands <duncan.sands@...h.u-psud.fr>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.

On 31/01/07 14:27, Duncan Sands wrote:
>> 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.
> 

I've had it polling every 200ms on a dual ppro200 since november, and it has never failed to poll the status.


> Ciao,
> 
> Duncan.


-- 
Simon Arlott


Download attachment "signature.asc" of type "application/pgp-signature" (830 bytes)