Hi there, yea, I also want to join this endless pipe discussion! ;)
We ran into troubles here due to large messages that should be sent via native pipes. Large means larger than the default message heap, the system heap, of the pipe subsystem so far. That raised the question why we should not provide some interface (and the required internal patches) to maintain per-pipe heaps. At least optional. This would allow to create pipe channels with even some megabyte space as we used them under RTAI. I would provide the required patches, but I'm not yet sure if we better extend rt_pipe_create with an additional parameter bufsize (0 = default, i.e. system heap, 0 > allocate per kmalloc or vmalloc) or if we add another function like rt_pipe_bufsize to allocate a dedicated heap after creation. Ideas, comments? Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
