On 8/10/2016 11:51 AM, Ferruh Yigit wrote:
> Hi Gopakumar,
>
> On 8/4/2016 5:14 PM, Ferruh Yigit wrote:
>> On 8/1/2016 10:19 PM, Gopakumar Choorakkot Edakkunni wrote:
>>> Well, for my purpose I just ended up creating a seperate/smaller pool
>>> earlier during bootup to try to guarantee its from on
Thank you Ferruh, I will give this a spin over the weekend and let you know.
Rgds,
Gopa.
On Thu, Aug 25, 2016 at 6:51 AM, Ferruh Yigit
wrote:
> On 8/10/2016 11:51 AM, Ferruh Yigit wrote:
> > Hi Gopakumar,
> >
> > On 8/4/2016 5:14 PM, Ferruh Yigit wrote:
> >> On 8/1/2016 10:19 PM, Gopakumar Choo
Hi Gopakumar,
On 8/4/2016 5:14 PM, Ferruh Yigit wrote:
> On 8/1/2016 10:19 PM, Gopakumar Choorakkot Edakkunni wrote:
>> 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 rest
On 8/1/2016 10:19 PM, Gopakumar Choorakkot Edakkunni wrote:
> 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 "fi
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 restrict
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
6 matches
Mail list logo
