From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, ALeX Wang <ee07b291@gmail.com>
Subject: Re: [dpdk-dev] [4.4 kernel] kni lockup, kernel dump
Date: Thu, 14 Apr 2016 16:43:50 +0200 [thread overview]
Message-ID: <1933005.8eilLGqekQ@xps13> (raw)
In-Reply-To: <570FA930.60105@intel.com>
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
next prev parent reply other threads:[~2016-04-14 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 0:19 ALeX Wang
2016-04-13 0:28 ` ALeX Wang
2016-04-13 22:26 ` ALeX Wang
2016-04-14 14:29 ` Ferruh Yigit
2016-04-14 14:43 ` Thomas Monjalon [this message]
2016-04-14 22:02 ` ALeX Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1933005.8eilLGqekQ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ee07b291@gmail.com \
--cc=ferruh.yigit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).