On Thu, 4 Jan 2007, Jens Alfke wrote: > That doesn't sound right. Blocking I/O shouldn't consume any more CPU than > non-blocking. If the worker thread is blocked waiting for data to arrive (or > be sent), it should be inside a system call, probably read(), consuming no > CPU.
The code has possible busy loops at a few places. I hope my work will address at least some of them. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
