dpdk: mempool priv intialization must be done before releasing buffers to pool 63/12763/5
authorSachin Saxena <sachin.saxena@nxp.com>
Mon, 28 May 2018 09:15:34 +0000 (14:45 +0530)
committerDamjan Marion <dmarion.lists@gmail.com>
Tue, 29 May 2018 14:44:21 +0000 (14:44 +0000)
commit0a77040fa0f588f3c2d539aa1d3c500731520676
tree4771c1869cfb366c9383223300b6b8375204e9e4
parentf706b8d79a6ef594057f27c9066bd5beb72c36b4
dpdk: mempool priv intialization must be done before releasing buffers to pool

 - Currently mempool priv size is getting initialized after releasing buffers
   to pool. This is causing mismatch in expected & real metadata size value
   and buffers are getting released with wrong offset. (when metadata offset
   is in use for a given platform)
 - Since private data size is 0 initially, metadata size don't include space
   for VLIB_BUFFER_HDR.

Change-Id: I780c4d518104631a3dcf192185bacf58b3598e65
Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com>
src/plugins/dpdk/buffer.c