infn-ke
infn-ke
When will this reach master? Looks like this is still on branch? And PR is more than a year old.
Thanks for confirming the shared memory size requirements! The parameters `RL_BUFFER_COUNT` and `RL_BUFFER_PAYLOAD_SIZE ` seems to have the requirement of the being a power of 2, like this; ```c #define...
My problem is that it seems to me that I'm only able to use about half of the shared memory given the constraints on these parameters. Assume I have 4...
> > I am afraid we can't do anything with that, that's the rpmsg design. Sometimes it is not easy to find the optimal way of shared memory use, would...
> > RPMsg_Lite is binary compatible with the Linux rpmsg driver, because the Linux implementation requires the vring alignment to 4KB (0x1000) the same alignment needs to be set on...
> I meant if you would be able to allocate 6kB, you would fit into this shared memory size with 4 buffers (RL_BUFFER_COUNT 2) of 496 bytes size, if this...
What are the requirements on `VRING_SIZE`, does that have to be a power of 2? Or we can take the exact number from the `vring_size`? E.g. if I do `vring_size`...
> Hi @infn-ke , it seems the VRING_SIZE does not need to be a power of 2, you could take 230 as calculated by vring_size() function. Thanks for confirming! Then...
Looks like same limitation also applies to the server side? Server only supports one transport layer, but can handle multiple services? Is that a valid statement? No simple way for...
Is there a roadmap to fix the client context issue? Multi-client support from one process is quite common use case.