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 for Android: free password hash cracker in your pocket

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

Message-ID: <45CF46B6.1060401@simon.arlott.org.uk>
Date:	Sun, 11 Feb 2007 16:39:18 +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 18:15, Duncan Sands wrote:
>> I've had it polling every 200ms on a dual ppro200 since november,
>> and it has never failed to poll the status. 
> 
> Great, that's certainly better than the speedtouch ;)
> I can't help feeling that polling twice a second is overkill.
> How about changing it to poll every 5 seconds if the line is
> up, and ten times as fast (as in this patch) if the line is
> down?  Also, what is the point of polling fast?  Does it matter
> if you miss some down-try_to_activate transitions?

It needs to be at most 2 seconds while down or it's going to miss some of the state changes, why bother to output all the types of state if you're going to ignore some of them?

As for while it's up, polling more often has a negligible effect on performance (still polling every 200ms here). If you change the timing for different states, you should know that it won't go into the down state on a retrain so ~up should enable faster polling.

-- 
Simon Arlott

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