From: torbenh <torbenh@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] jack: use eventfd which never blocks.
Date: Mon, 22 Nov 2010 16:04:31 +0100 [thread overview]
Message-ID: <20101122150431.GO4646@siel.b> (raw)
In-Reply-To: <1290431349.2382.2.camel@patrakov-desktop>
On Mon, Nov 22, 2010 at 06:09:09PM +0500, Alexander E. Patrakov wrote:
> torbenh wrote:
> > i think in the case of mmap, there are one byte written -> advance one
> > period rules. these promises are not kept, when the write end is made
> > non-blocking.
>
> I was not aware of such rules. So, please disregard my review.
(i am not aware of them either....
but this is the only real explanation i have, why things go wrong.
with the O_NONBLOCK patch and flash)
and also why the read does not eat all data thats in the pipe)
>
> --
> Alexander E. Patrakov
>
--
torben Hohn
prev parent reply other threads:[~2010-11-22 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 14:22 [PATCH] jack: use eventfd which never blocks Torben Hohn
2010-11-21 10:15 ` Alexander E. Patrakov
[not found] ` <20101122121518.GM4646@siel.b>
2010-11-22 13:09 ` Alexander E. Patrakov
2010-11-22 15:04 ` torbenh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101122150431.GO4646@siel.b \
--to=torbenh@gmx.de \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox