From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5457DF1C.4060209@xenomai.org> Date: Mon, 03 Nov 2014 21:01:32 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <94331816.zv1NYeHro4@riemann> <20141031200007.GC378@sumost.ca> <5454ADDF.4040604@xenomai.org> <6071747.2uXMl1ZSO0@riemann> <54573A6D.1030201@xenomai.org> <20141103155947.GA15262@sumost.ca> <5457AD81.7090200@xenomai.org> <20141103183747.GB15262@sumost.ca> In-Reply-To: <20141103183747.GB15262@sumost.ca> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Message Pipe services behaviour List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Steve M. Robbins" Cc: Xenomai@xenomai.org On 11/03/2014 07:37 PM, Steve M. Robbins wrote: > On Mon, Nov 03, 2014 at 05:29:53PM +0100, Philippe Gerum wrote: > >> Just to make sure we are on the same page, as Dietmar mentioned in an >> earlier mail, read() as implemented by the rt-pipe driver only returns >> _one_ message at a time, although > 1 could be pending. One has to >> iterate over a read() loop using a non-blocking fd on the /dev/rtp >> device to get them all. > > Aha! Thanks (and to Dietmar). I completely missed this fact. I'll > go re-write the read as a loop and see if it works better. I should read > until the read() returns 0 (bytes read)? > Until you get -1 with errno == EWOULDBLOCK. Zero would rather mean that the other end of pipe has been disconnected, just like with a regular FIFO. -- Philippe.