[dpdk-dev] rte_mbuf.next in 2nd cacheline

Bruce Richardson bruce.richardson at intel.com
Mon Jun 15 18:02:09 CEST 2015


On Mon, Jun 15, 2015 at 04:59:55PM +0100, Ananyev, Konstantin wrote:
> 
> 
> 
> As I can see, vector TX is the only one that calls __rte_pktmbuf_prefree_seg() directly.
> All others use rte_pktmbuf_free_seg(), that does ' m->next = NULL' anyway.
> For vector TX - yes, need to verify that it would not introduce a slowdown.
> Konstantin
>

But if the function is only directly called from one place, and that doesn't
have a problem, why would we bother making any change at all?

/Bruce


More information about the dev mailing list