From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [4.4 kernel] kni lockup, kernel dump Date: Thu, 14 Apr 2016 16:43:50 +0200 Message-ID: <1933005.8eilLGqekQ@xps13> References: <570FA930.60105@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ALeX Wang To: Ferruh Yigit Return-path: Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by dpdk.org (Postfix) with ESMTP id 1701329B6 for ; Thu, 14 Apr 2016 16:43:53 +0200 (CEST) Received: by mail-wm0-f47.google.com with SMTP id n3so129661949wmn.0 for ; Thu, 14 Apr 2016 07:43:53 -0700 (PDT) In-Reply-To: <570FA930.60105@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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