conduit load latency




I just experienced a situation where high system load (actually everything was
running verrryyy slow due to interrupt flooding) caused gpilotd to abort just
after 
gpilotd-ERROR **: Unable to open conduit!
I believe this would be the backup conduit.

>From a user standpoint it looks like the delay in the load caused gpilotd to
assume it failed. From memory i'd say it uses dlopen() whom doesn't care less
about getting stoped in a mmap by a swapin. 

anyone has a light ? :)

-- 
Carlos Morgado - chbm(at)chbm(dot)nu - http://chbm.nu/ -- gpgkey: 0x1FC57F0A
http://wwwkeys.pgp.net/ FP:0A27 35D3 C448 3641 0573 6876 2A37 4BB2 1FC5 7F0A
Software is like sex; it's better when it's free. - Linus Torvalds



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]