From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id A905F2986
 for <dev@dpdk.org>; Thu, 14 Apr 2016 16:29:37 +0200 (CEST)
Received: from orsmga003.jf.intel.com ([10.7.209.27])
 by orsmga101.jf.intel.com with ESMTP; 14 Apr 2016 07:29:05 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.24,485,1455004800"; d="scan'208";a="784873397"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.28])
 ([10.237.220.28])
 by orsmga003.jf.intel.com with ESMTP; 14 Apr 2016 07:29:05 -0700
To: ALeX Wang <ee07b291@gmail.com>, dev@dpdk.org
References: <CANmyKO5bLFZA=o=K5wWdvKkzd_epy_2uriH8QqCdsMTFuuCEtg@mail.gmail.com>
 <CANmyKO6PB+zFcaJAMQonauvj66fwXPxDnMVfKDq3zc1vDvkuxg@mail.gmail.com>
 <CANmyKO7oUowb3Ubg8p26Spc68wEMfFuSBxOyauUG0jgophp_Gg@mail.gmail.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <570FA930.60105@intel.com>
Date: Thu, 14 Apr 2016 15:29:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CANmyKO7oUowb3Ubg8p26Spc68wEMfFuSBxOyauUG0jgophp_Gg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-dev] [4.4 kernel] kni lockup, kernel dump
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2016 14:29:38 -0000

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.

Regards,
ferruh