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: <200701311527.39343.duncan.sands@math.u-psud.fr>
Date:	Wed, 31 Jan 2007 15:27:36 +0100
From:	Duncan Sands <duncan.sands@...h.u-psud.fr>
To:	Simon Arlott <3d1f88d2534993eb311hc0vm0003uvpw@...nder.lp0.eu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.

> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/