> From: Philippe Gerum [mailto:[email protected]] > Sent: Wednesday, April 27, 2011 11:43 PM > > On Wed, 2011-04-27 at 14:22 +0200, [email protected] > wrote: > > ... Wouldn't it be desirable to implement the > > readv file operation in the rtpipe driver so that the guarantee "One > > read() per rt_pipe_write()" could cover readv(2) also? > > No objection to merge this. Patch welcome.
Well, I'll try to come up with one. > > (Besides, this > > would make the phrase "Operates just like read" in the readv(2) man page > > more correct.) > > Having readv() operate like read() would not give any guarantee wrt > message boundaries, because it is the real-time write side which makes > the decision regarding this, not the read side. So you could have > readv() operate like read() and still have blurred boundaries in case > rt_pipe_stream() is used instead of rt_pipe_write(). You are of course right, and what you wrote about readv also applies to read. -- Dietmar -------------------------------------------------------- manroland AG Vorsitzender des Aufsichtsrates: Hanno C. Fiedler Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592 USt-Ident-Nr. DE 250200933 _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
