> From: [email protected] [mailto:[email protected]] > On Behalf Of [email protected] > Sent: Wednesday, April 27, 2011 10:50 AM > > > From: [email protected] > > On Behalf Of Philippe Gerum > > Sent: Tuesday, April 26, 2011 10:28 PM > > > > ... > > One read() per rt_pipe_write() operation, always. > > Thank you for your answer. Is "One readv() per rt_pipe_write() > operation" supposed to be true also, or is there something special to be > taken into consideration regarding readv(2)?
Meanwhile, I found some facts which allow me to elaborate on my question. The rtpipe device hasn't a readv file operation implemented, so the kernel substitutes the readv call by a series of read calls to the device driver; due to this, under certain circumstances readv(2) gathers more than a single rt_pipe_write() call's data. (I can provide an example case, if desired.) 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? (Besides, this would make the phrase "Operates just like read" in the readv(2) man page more correct.) -- 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
