Re: [dpdk-dev] [PATCH] kni: dynamically allocate memory for each KNI

On 8/29/2018 10:52 AM, Igor Ryzhov wrote: > Hello Ferruh, > > Thanks for the review, comments inline. > > On Mon, Aug 27, 2018 at 8:06 PM, Ferruh Yigit > wrote: > > On 8/2/2018 3:25 PM, Igor Ryzhov wrote: > > Long time ago preallocation of memory for KNI w

Re: [dpdk-dev] [PATCH] kni: dynamically allocate memory for each KNI

Hello Ferruh, Thanks for the review, comments inline. On Mon, Aug 27, 2018 at 8:06 PM, Ferruh Yigit wrote: > On 8/2/2018 3:25 PM, Igor Ryzhov wrote: > > Long time ago preallocation of memory for KNI was introduced in commit > > 0c6bc8e. It was done because of lack of ability to free previously

Re: [dpdk-dev] [PATCH] kni: dynamically allocate memory for each KNI

On 8/2/2018 3:25 PM, Igor Ryzhov wrote: > Long time ago preallocation of memory for KNI was introduced in commit > 0c6bc8e. It was done because of lack of ability to free previously > allocated memzones, which led to memzone exhaustion. Currently memzones > can be freed and this patch uses this abi

[dpdk-dev] [PATCH] kni: dynamically allocate memory for each KNI

Long time ago preallocation of memory for KNI was introduced in commit 0c6bc8e. It was done because of lack of ability to free previously allocated memzones, which led to memzone exhaustion. Currently memzones can be freed and this patch uses this ability for dynamic KNI memory allocation. Signed-