[dpdk-dev] [4.4 kernel] kni lockup, kernel dump

[Thomas Monjalon]

2016-04-14 15:29, Ferruh Yigit:
> On 4/13/2016 11:26 PM, ALeX Wang wrote:
> > Did more experiment, found that it has nothing to do with the kernel
> > version,
> > 
> > It only happens when using kni module with '--no-huge' eal flag...
> > 
> > Is that expected?
> > 
> 
> Yes.
> KNI kernel module expects mempool is physically continuous, with
> '--no-huge' flag this is no more true, and as a result KNI module can
> access to incorrect address.

This is a bug.
The memory API should allow to explicit this restriction and return
an error if it cannot offer the requested continuous memory.
See this thread for discussion:
	http://dpdk.org/ml/archives/dev/2016-April/037444.html