search for: poolinterval

On Nov 25, 2013, at 4:56 PM, Fabio Cecamore wrote: > Hi all, > after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: > > [...] > [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 "ret

.... Do you have any profiling data to show how much more CPU time is being used? I don't have any profiling data, I just noticed that blazer_usb is ever first in 'top' list, with older blazer driver it was at the end of the 'top' list, now it uses always 0,3% to 1,7% of CPU with poolinterval at 2 seconds. My CPU is not so powerful but anyway it is a good diference and so I noted it.. Bye -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131126/7460de4b/attachment.html>

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8