On 27 April 2015 at 21:23, Bill Fischofer <bill.fischo...@linaro.org> wrote:
> IPCs should be short messages used either as "shoulder taps" or for brief > communication. If a larger data structure is needed, a pointer to it can be > passed ar s the IPC message, > Sender and receiver would normally not be located in the same address space. Also passing a pointer to some external data structure creates the problem of knowing when and how to free that data structure. > so again the interpretation of the IPC message contents would generally be > up to the application, with perhaps some basic message type decoding > provided by the APIs. > I think an IPC API needs to give the user the ability to send messages to different endpoints. Also the receiver must be able to identify the sender of a message. Message structure and content should be outside the responsibilities of the IPC API. > On Mon, Apr 27, 2015 at 9:18 AM, Ola Liljedahl <ola.liljed...@linaro.org> > wrote: > >> I am also interested in IPC (between control and dataplane) but not for >> packets but for messages (so more like buffers). I don't see that these IPC >> messages should be parsed and classified like packets and I don't need the >> packet_flags.h API either. >> >> However pktio seems like the only abstraction that allows for an ODP >> application to communicate (send/receive data) with the outside (where is >> bufio?) so is perhaps the mechanism to use anyway. The application would >> have to know that "packets" received from a certain pktio interface >> (through queues/scheduler) are not really packets but messages and need to >> be treated differently. >> >> On 23 April 2015 at 19:46, Maxim Uvarov <maxim.uva...@linaro.org> wrote: >> >>> Since nobody replayed on rfc patch I did clean up and splitting it >>> on several patches. >>> >>> Please consider this version for review. >>> >>> Thanks, >>> Maxim. >>> >>> Maxim Uvarov (7): >>> linux-generic: zero params for pool create >>> api: ipc: shared memory add no create flag >>> api ipc: update ring with shm proc argument >>> linux-generic: reflect shm flags and add mode debug prints >>> linux-generic: ipc init odp ring >>> linux-generic: add ipc pktio support >>> ipc: example app >>> >>> configure.ac | 1 + >>> example/Makefile.am | 2 +- >>> example/ipc/.gitignore | 1 + >>> example/ipc/Makefile.am | 7 + >>> example/ipc/odp_ipc.c | 441 +++++++++++++++ >>> helper/include/odp/helper/ring.h | 2 + >>> helper/ring.c | 9 +- >>> include/odp/api/pool.h | 1 + >>> include/odp/api/shared_memory.h | 1 + >>> platform/linux-generic/Makefile.am | 2 + >>> .../linux-generic/include/odp_buffer_internal.h | 3 + >>> .../linux-generic/include/odp_packet_io_internal.h | 15 + >>> .../include/odp_packet_io_ipc_internal.h | 47 ++ >>> platform/linux-generic/odp_init.c | 6 + >>> platform/linux-generic/odp_packet_io.c | 30 +- >>> platform/linux-generic/odp_packet_io_ipc.c | 590 >>> +++++++++++++++++++++ >>> platform/linux-generic/odp_pool.c | 16 +- >>> platform/linux-generic/odp_schedule.c | 1 + >>> platform/linux-generic/odp_shared_memory.c | 9 +- >>> test/validation/odp_queue.c | 1 + >>> 20 files changed, 1177 insertions(+), 8 deletions(-) >>> create mode 100644 example/ipc/.gitignore >>> create mode 100644 example/ipc/Makefile.am >>> create mode 100644 example/ipc/odp_ipc.c >>> create mode 100644 >>> platform/linux-generic/include/odp_packet_io_ipc_internal.h >>> create mode 100644 platform/linux-generic/odp_packet_io_ipc.c >>> >>> -- >>> 1.9.1 >>> >>> _______________________________________________ >>> lng-odp mailing list >>> lng-odp@lists.linaro.org >>> https://lists.linaro.org/mailman/listinfo/lng-odp >>> >> >> >> _______________________________________________ >> lng-odp mailing list >> lng-odp@lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/lng-odp >> >> >
_______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
