This patch series fixes a number of issues that I discovered trying
to use odp-dpdk with openvswitch.

For starters the Makefile.am in linux-dpdk did not intall the correct files. 

Then there were a lot of problems in the API implementation that made them
unusable by any external application. Things like getting the packet length,
getting to the packet payload and many more.

I also discovered that setup_pkt_dpdk made the assumption that there were
always two interfaces present and it configured the queue ids based on this.

There is most likely more work to be done, as I haven't been able to get 
packets going out from OVS. The cause of it may be the process context from 
where the packets are sent.

Also I haven't worked on the ipsec implementation, but with these changes in 
the buffer management that shouldn't be hard to implement and test.

Ciprian Barbu (2):
  linux-dpdk: Fixed the installed include files
  linux-dpdk: Rework buffer management

 platform/linux-dpdk/Makefile.am                    |  10 +-
 platform/linux-dpdk/include/api/odp_buffer.h       |   2 +-
 platform/linux-dpdk/include/api/odp_buffer_pool.h  |   2 +-
 platform/linux-dpdk/include/api/odp_packet.h       |  17 +
 platform/linux-dpdk/include/odp_buffer_internal.h  |   8 +-
 platform/linux-dpdk/include/odp_packet_internal.h  |   7 +-
 .../linux-dpdk/include/odp_packet_io_internal.h    |   5 -
 platform/linux-dpdk/odp_buffer.c                   |  26 +-
 platform/linux-dpdk/odp_buffer_pool.c              | 150 +++++++-
 platform/linux-dpdk/odp_packet.c                   | 148 +++++---
 platform/linux-dpdk/odp_packet_dpdk.c              |  17 +-
 platform/linux-dpdk/odp_queue.c                    |  20 +-
 platform/linux-dpdk/odp_schedule.c                 | 417 +++++++++++++++++++++
 13 files changed, 721 insertions(+), 108 deletions(-)
 create mode 100644 platform/linux-dpdk/odp_schedule.c

-- 
1.8.3.2


_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to