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
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 involv
> 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, an
> 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 p
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.
Signed-off-by: Simon Arlott <[EMAIL PROTECTED]>
---
drivers/usb/atm/cxacru.c |2 +-
5 matches
Mail list logo
