Subject: Re: [libssh2] Non Blocking Status

Re: [libssh2] Non Blocking Status

From: Daniel Stenberg <>
Date: Fri, 5 Jan 2007 16:42:50 +0100 (CET)

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's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
libssh2-devel mailing list
Received on 2007-01-05