This discussion is about improving performance of specific use cases by moving the mbuf fields when needed. We could consider how to configure it and how complicated it would be to write applications or drivers (especially vector ones) for such a moving structure. But it is simpler to say that having an API depending of some options is a "no-design" which could seriously slow down the DPDK adoption. You can have a different opinion but I cannot imagine how strong must be the arguments to make it happen.
- [dpdk-dev] Reshuffling of rte_mbuf struct... shesha Sreenivasamurthy (shesha)
- [dpdk-dev] Reshuffling of rte_mbuf s... Arnon Warshavsky
- [dpdk-dev] Reshuffling of rte_mb... Stephen Hemminger
- [dpdk-dev] Reshuffling of rt... shesha Sreenivasamurthy (shesha)
- [dpdk-dev] Reshuffling o... Arnon Warshavsky
- [dpdk-dev] Reshuffl... shesha Sreenivasamurthy (shesha)
- [dpdk-dev] Resh... Thomas Monjalon
- [dpdk-dev] ... Matthew Hall
- [dpdk-dev] ... Bruce Richardson
- [dpdk-dev] ... Zoltan Kiss
- [dpdk-dev] ... Matthew Hall
- [dpdk-dev] ... shesha Sreenivasamurthy (shesha)