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:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- From: Duncan Sands <[email protected]>
- Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- References:
- [PATCH 2/3] cxacru: Poll for device status more frequently.
- From: Simon Arlott <[email protected]>
- Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- From: Duncan Sands <[email protected]>
- [PATCH 2/3] cxacru: Poll for device status more frequently.
- Prev by Date: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- Next by Date: Re: [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.
- Previous by thread: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- Next by thread: Re: [PATCH 2/3] cxacru: Poll for device status more frequently.
- Index(es):
 |