[dpdk-dev] [PATCH] xenvirt: fix compilation after mempool changes

2016-06-13 Thread Olivier Matz
On 06/13/2016 11:10 AM, Christian Ehrhardt wrote: > Hmm, > Hi again Oliver. > > I was too fast saying yes. > I don't know what is different now but I clearly tested it wrong the > first time. > Now I get: > > CC rte_xen_lib.o >

[dpdk-dev] [PATCH] xenvirt: fix compilation after mempool changes

2016-06-13 Thread Christian Ehrhardt
Hmm, Hi again Oliver. I was too fast saying yes. I don't know what is different now but I clearly tested it wrong the first time. Now I get: CC rte_xen_lib.o /mnt/nvme/dpdk-16-07-pre-linking/drivers/net/xenvirt/rte_xen_lib.c: In function ?grant_gntalloc_mbuf_pool?:

[dpdk-dev] [PATCH] xenvirt: fix compilation after mempool changes

2016-06-13 Thread Christian Ehrhardt
Hi Oliver, thanks for the fast response! It fixes the compilation issue and I totally agree to your argument of the multi-chunk issues being out of scope for this as they never worked. Unfortunately I lack an environment to actually test this in real-life if we need any more follow up than this.

[dpdk-dev] [PATCH] xenvirt: fix compilation after mempool changes

2016-06-13 Thread Olivier Matz
The field elt_va_start has been removed from the mempool structure, and it was not replaced in xenvirt. Fix this by getting the mempool objects address by using the address of the first memory chunk list. Note that it won't work with mempool composed of several chunks, but it was already the