> >Currently, OVS only support DPDK single segment mbuf, >it could lead problems, like a large non-DPDK source >packet transmit to dpdk port. > >Also, OVS doesn't copy enough info in mbuf when do >packet copy. > >At the same time, vlan and tunnelling packet's DPDK >offloads, for example TSO, needs multi-segment mbuf's >support. > >This patchset solved all above issues.
Hi Michael, Thanks for this patch - I'm also working in this area currently, and have an RFC patch that builds on your work. I'm interested in the NIC that you used in testing this patchset - specifically, the related TX callback function that was used. The reason I ask is that vectorized Tx functions are typically incompatible with multi-segment mbufs, due to their scatter-gather (i.e. non-contiguous) nature, although this may vary from PMD to PMD. Finally, this patch doesn't provide support for multi-segment jumbo frames that originate from a DPDK source - I'll post an RFC patch on this tomorrow, and I would be grateful if you could review same! Thanks again, Mark > >-- >v1 --> v2 > rebase code to newest upstream. > fix some typo in commit log. > >Michael Qiu (5): > lib/dp-packet: init the mbuf to zero when build with DPDK > lib/dp-packet: copy additional packet info when do packet copy > lib/dp-packet: Fix data_len issue with multi-segments > lib/dp-packet: copy multi-segments data from DPDK mbuf > lib/netdev-dpdk: copy large packet to multi-segment mbufs > > lib/dp-packet.c | 33 ++++++++++++++++++++++++++++++--- > lib/dp-packet.h | 23 +++++++++++++---------- > lib/netdev-dpdk.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++---- > 3 files changed, 94 insertions(+), 17 deletions(-) > >-- >1.8.3.1 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
