From: Simon Arlott <simon@arlott.org>
To: Duncan Sands <duncan.sands@math.u-psud.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
Date: Sun, 11 Feb 2007 16:39:18 +0000 [thread overview]
Message-ID: <45CF46B6.1060401@simon.arlott.org.uk> (raw)
In-Reply-To: <200701311915.42340.duncan.sands@math.u-psud.fr>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 829 bytes --]
prev parent reply other threads:[~2007-02-11 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 21:27 [PATCH 2/3] cxacru: Poll for device status more frequently Simon Arlott
2007-01-31 14:27 ` Duncan Sands
2007-01-31 17:46 ` Simon Arlott
2007-01-31 18:15 ` Duncan Sands
2007-02-11 16:39 ` Simon Arlott [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45CF46B6.1060401@simon.arlott.org.uk \
--to=simon@arlott.org \
--cc=567c60ddd62e6ee0961hghjy0007txcf@thunder.lp0.eu \
--cc=duncan.sands@math.u-psud.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.