* Marc Lehmann schm...@schmorp.de [13/01/24 11:18]:
On Wed, Jan 23, 2013 at 06:11:20PM +0400, Konstantin Osipov
kos...@tarantool.org wrote:
* Marc Lehmann schm...@schmorp.de [13/01/23 17:50]:
Note also that the solution to having your own threadpool is simply...
having your own
On Thu, Jan 24, 2013 at 02:17:49PM +0400, Konstantin Osipov wrote:
There is a win for us since there is no other library out there
which can do async getaddrinfo() and integrate well into libev
event loop.
You might want to consider Chroboczeck's threadpool, designed exactly for this
purpose
On Thu, Jan 24, 2013 at 02:17:49PM +0400, Konstantin Osipov
kos...@tarantool.org wrote:
Forking libeio is and (has always been with free software)
an obvious option.
For these we need a reliable thread-pool of gophers, i.e.
performers of random tasks, and libeio eio_custom fits here
* Marc Lehmann schm...@schmorp.de [13/01/24 11:18]:
While this is completely unrelated, this is wrong on so many levels:
1. 64 bit pointers don't give you millions of stacks, they are a
requirement, but not sufficient. For example, on very common
amd64 hardware your address space is
* Marc Lehmann schm...@schmorp.de [13/01/23 17:50]:
Note also that the solution to having your own threadpool is simply...
having your own threadpool.
Forking libeio is and (has always been with free software)
an obvious option.
I'm immensely thankful to you for libeio - it has already saved us
Hi,
libeio manual says that EIO_STACKSIZE, if set to 0, leaves
pthread stack size at its default value:
--quote
If it is defined, but 0, then the default operating system stack
size will be used.
--end quote
In fact, if EIO_STACKSIZE is defined, but 0, the stack size used
is PTHREAD_STACK_MIN:
On Fri, Jan 18, 2013 at 09:54:02PM +0400, Konstantin Osipov
kostja.osi...@gmail.com wrote:
libeio manual says that EIO_STACKSIZE, if set to 0, leaves
pthread stack size at its default value:
Thats a (documentation) bug, thanks for pointing it out.
It seems that all that is necessary is to
