On 12/31/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 31.12.2005 um 20:12 schrieb Vlad Seryakov:
>
> > aio_read/aio_write system calls look like supported ubnder Linux
> >
>
> yes. most of modern os's support some kind of kaio.
> I have checked solaris, linux and darwin and all do.
Hmm
On 1/1/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> Another solution to reduce locking, just to allocate maxconn structures
> with its own mutex and perform locking for particular struct only, so
> writers will not block other writers, only writer/reader. More memory
> but less concurrency.
>
> I
Another solution to reduce locking, just to allocate maxconn structures
with its own mutex and perform locking for particular struct only, so
writers will not block other writers, only writer/reader. More memory
but less concurrency.
I will try this tomorrow.
Zoran Vasiljevic wrote:
Am 31.1
Tried it, nsd started crashing and i am guessing that the problem is
combination of aio_write and mmap.
When is start spooling, i just submit aio_write and return immediately,
so there are a lot of quick aio_write calls. By the time i reach mmap,
it looks like it's always ahead of actual writing
