«

Hi,
I'm developing a server application , and i've notice that on
heavy-load (8000 HTTP transaction/sec , few hundredconcurrent
connections ) i'm starting to loose connection .

Since i'm using nonblocking I/O (poll for kernel 2.4 and epoll for
kernel 2.60) i suspect that the problem lies in my accept threads . i
have 2 listenning threads that looks pretty much like:
{
lock_mutex();
s=accept(); // blocking accept
unlock_mutext();
post_socket(s); // put socket in queue for processing in
other threads...
}

Now, i really don't know if i can remove the mutex stuff . The Man
pages says nothing about the accept() thread-safeness (except the HPUX
, but it's not the standard ).

Can i skip the mutex ? is it depend on the kernel ?
thnx,
zvi fer

Of course i meant "listening" , and not "listenning".... damn keyboard
...
(E-Mail Removed) wrote:
> Hi,
> I'm developing a server application , and i've notice that on
> heavy-load (8000 HTTP transaction/sec , few hundredconcurrent
> connections ) i'm starting to loose connection .
>
> Since i'm using nonblocking I/O (poll for kernel 2.4 and epoll for
> kernel 2.60) i suspect that the problem lies in my accept threads . i
> have 2 listenning threads that looks pretty much like:
> {
> lock_mutex();
> s=accept(); // blocking accept
> unlock_mutext();
> post_socket(s); // put socket in queue for processing in
> other threads...
> }
>
> Now, i really don't know if i can remove the mutex stuff . The Man
> pages says nothing about the accept() thread-safeness (except the HPUX
> , but it's not the standard ).
>
> Can i skip the mutex ? is it depend on the kernel ?
> thnx,
> zvi fer