mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Wed, 31 Jan 2007 17:46:42 +0000	[thread overview]
Message-ID: <45C0D602.70708@simon.arlott.org.uk> (raw)
In-Reply-To: <200701311527.39343.duncan.sands@math.u-psud.fr>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 829 bytes --]

  reply	other threads:[~2007-01-31 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 21:27 Simon Arlott
2007-01-31 14:27 ` Duncan Sands
2007-01-31 17:46   ` Simon Arlott [this message]
2007-01-31 18:15     ` Duncan Sands
2007-02-11 16:39       ` Simon Arlott

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=45C0D602.70708@simon.arlott.org.uk \
    --to=simon@arlott.org \
    --cc=b3c83437033a245c3e1hcjxk0000jq7l@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome