Re: [naviserver-devel] Upload Progress

[Zoran V. <zv...@ar...>]

Am 02.01.2006 um 17:23 schrieb Stephen Deasey:

>> So, what is the problem?
>
>
> http://www.gnu.org/software/libc/manual/html_node/Configuration-of- 
> AIO.html
>

Still, where is the problem? The fact that Linux implements them as
userlevel thread does not mean much to me.

On Solaris, each thread you start results in an LWP in the kernel.
At least this is so if you use the naviserver thread abstraction.
This is not cheap, hence I'm not very fond of starting threads
with or without the Tcl interp, as all threads are actually expensive.
(the former are more expensive though).

On Linux, especially with NPTL, threads are rather cheap, so
there you can easily add yet-another-thread and handle the spooling
with a dedicated thread or pool of threads.

But... what is the MAIN reason against AIO? Why would not that be
a platform-neutral simple way of doing a non-blocking writing from
within our driver-thread? Provided we have a simple and workable
abstract solution (aio_xxx family of routines) which is thread-safe,
why would we bother about the per-platform implementation of it?

???

Zoran