-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/01/2014 11:34 AM, Iñaki Baz Castillo wrote: > There should be a public API for setting/getting the threadpool > size. Is that hard to achieve? >
What if threads are blocked doing something and you shrink the threadpool? How do we "kill" those threads? If you are thinking about using signals, what if they are doing CPU-intensive work? Ideally we would have 2 threadpools, one for our internal things (getaddrinfo, getnameinfo and fs) and another one for the user to play with, via uv_queue_work. This would still not solve all problems though. Time is a scarce resource, unfortunately, but patches are always welcome. - -- Saúl Ibarra Corretgé bettercallsaghul.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBAgAGBQJTsoMCAAoJEEEOVVOum8BZgscP/0FnDLR8iCGXmY7J54EnhviY Khwi9qN5rg4zJo/oKp9flingQf/soBR6BGkR6deofi4fuBnv9yH56bU89ANjnXwK BUBeEqAKIaP8fbWDDiE9eHeIiSkxLmGUciklkQc+C1qNVxdcaL7EOrCt/rZb6d7e X7Gp4jweM7D+yV4u5T19L/Ip39gQuyiJZ4zxyBiU0zvVS1Vq1C2IerqKF9knEvy6 mgjUQhSeDGJKD4RNoJENPeRzruwvLAHBlhWH15nNPKkyRhzJ6YgKKgQLzmKMU0US cpLB3TGn2aZa6JYJSQurZ5bQjsfuqZl4rR4wCxAgMzA5zp2SMm4qGUySxYciycVR PonmOOIoXsp0OfjeoAR2NyyCt8Yo/CmpH19Rx1L080QIZapCDD41B4H/IcjUBXrj VjSUXbuVWMkB6IcwDTtOvfz2qu1KOF2gOoj52kKNIYPPdfdz7a7vDUQIIRT89LF4 9D9qleBtQ2HZ1WcunFF56XcnwY2vErOBNofEem/DYWCO8cZE8vuWjujcJXCKzEx7 46LrQ8/Va2oNRQu6kWGJ2/gzvw2JicdomI2cdLAA7kwQoo4UPD/qEjnisyNDmVDy YnDo8m8VdNF+P+7/wsKKMWWOANHfy3wXtkoeyb4Z4phvLpCMYK+VK8ytG3xukdiJ eNGbadWHb+5m6RE92XM4 =15MX -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
