Re: [Xenomai-help] xnpipe EPOLLIN starvation

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

Filip Van Rillaer wrote:
> Hi,
>  
> I am transferring data from the Xenomai domain to the 2nd domain with
> the xenomai pipe.  In the 2nd domain I am using the epoll interface to
> wait for the arrival of new data.  The first time that data are written
> in the pipe at the Xenomai side, the 2nd domain receives the EPOLLIN (an
> that's OK).  But the 2nd time data are written in the pipe at the
> Xenomai side, the 2nd domain is NOT receiving EPOLLIN and therefore dies
> forever.
>  
> I am not familiar at all with the Xenomai internals, but I tried to
> gather some information: it look like when the first characters are
> written at the Xenomai side, the xnpipe_wakeup_proc calls
> xnpipe_dequeue_wait and this way it is removed forever from the
> waiters-queue.
> When I remove the "else"-instruction in xnpipe_poll so that
> xnpipe_wakeup_proc is called un-conditionally, then it works as expected
> ... however I have no idea if this patch is correct.  So please comment.
>  
> FYI:
> URL: http://svn.gna.org/svn/xenomai/trunk
> Repository Root: http://svn.gna.org/svn/xenomai
> Repository UUID: c6d672ea-8702-0410-b560-f74c916a59fe
> Revision: 4047

Are you sure you are not having a problem with "edge-triggered" versus
"level-triggered" notification ?
http://www.kegel.com/c10k.html#nb.edge
http://www.kegel.com/c10k.html#nb

-- 
                                                 Gilles.