Well, for my purpose I just ended up creating a seperate/smaller pool earlier during bootup to try to guarantee its from one memseg.
But I am assuming that this KNI restriction is something thats "currently" not fixed and is "fixable" ? Any ideas on what the summary of the reason for this restriction is - I was gonna check if I can fix that Rgds, Gopa. On Sat, Jul 30, 2016 at 10:39 PM, Gopakumar Choorakkot Edakkunni < gopakumar.c.e at gmail.com> wrote: > Hi all, > > So 16.07 seems to have an rte_mempool_create() which can allocate items > from multiple memzones (commit d1d914eb), which is awesome and is the > reason I upgraed to 16.07 !! > > But .. when I call rte_kni_alloc() with the mempool as parameter, theres a > check in there which says below > > /* KNI currently requires to have only one memory chunk */ > if (mp->nb_mem_chunks != 1) > goto kni_fail; > > And I hit that check because I am allocating a large mempool that happens > to span multiple memzones. I am perfectly fine with allocating a seperate > mempool just for KNI, except that I am unable to find any API or a flag or > some setting which says "create me a mempool that doesnt span memzones", > just so that I can use it with rte_kni_alloc() > > Any suggestions will be helpful ! > > Rgds, > Gopa. > >