http://bugzilla.novell.com/show_bug.cgi?id=470120
User [email protected] added comment http://bugzilla.novell.com/show_bug.cgi?id=470120#c11 Gonzalo Paniagua Javier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #11 from Gonzalo Paniagua Javier <[email protected]> 2009-07-22 10:07:18 MDT --- Benoit, someone tested the patch which checks for EWOULDBLOCK and put the socket back in the poll(). The result is a busy loop that takes a lot of CPU. 1) poll () -> socket ready to write 2) send () -> EWOULDBLOCK/EAGAIN 3) go to 1) If you have a fix to avoid this, patches are welcome. Otherwise, I'll close this as WONTFIX and suggest the use of non-blocking sockets as the effect that you get when using the threadpool is the same. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
