[mythtv] ringbuffer.cpp

Paul Kendall pkendall64 at gmail.com
Wed Feb 19 02:24:25 UTC 2014

On Wed, Feb 19, 2014 at 2:00 PM, Jean-Yves Avenard <jyavenard at gmail.com>wrote:

> I've summarised the issue being seen in this question:
> http://stackoverflow.com/questions/21868812/what-does-a-call-to-read-blocks-forever
> So at some stage, once the reader reach the end of the file, it
> returns with just the amount of bytes there's left between the current
> position and EOF.
> Immediately after you have another read for the remaining of the
> block. Only then will the writer write again.
> The following read is now blocking for a very long time.

Have you considered that the problem may be that we are flushing with
fdatasync and the metadata not being flushed may be causing the problem for
the reader thread?
It would be s simple thing to try by changing sync to a full sync.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-dev/attachments/20140219/f01d9c79/attachment.html>

More information about the mythtv-dev mailing list