DPDK usage discussions
 help / color / mirror / Atom feed
From: Nishant Verma <vnish11@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] KNI on 32 bit
Date: Sat, 8 Oct 2016 22:46:19 -0400	[thread overview]
Message-ID: <CAHhCjUEjwdZbetr-c2iE4zbQ3f023XoGDQSqgXrGbcteQ_DEAg@mail.gmail.com> (raw)
In-Reply-To: <2871637.lskxxgeZ0v@xps13>

But i am persuaded by this link.
http://dpdk.org/ml/archives/dev/2014-January/001143.html

If it really can't, then some one has to dismiss this as well.


On Fri, Oct 7, 2016 at 7:15 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 2016-10-07 17:46, Nishant Verma:
> > Hi All,
> >
> > My machine is 64 bit.
> > I am trying to compile DPDK 16.07 with i686. It's giving me error :
> > *"/cm_data/onewebcommon/data_fw/hfdp/script/intel-dpdk/lib/
> librte_port/rte_port_kni.c:38:21:
> > fatal error: rte_kni.h: No such file or directory"*
> >
> > Little bit of reading of previous question indicated  that in .config i
> > need to set the *CONFIG_RTE_LIBRTE_KNI=y* manually.
> >
> > I tried that too, but still getting same error.
> >
> > Any clue??????? to resolve the issue.
>
> See this config template:
>         http://dpdk.org/browse/dpdk/tree/config/defconfig_i686-
> native-linuxapp-gcc#n45
> "KNI is not supported on 32-bit"
>
> You should not see this error. See the makefile:
>         http://dpdk.org/browse/dpdk/tree/lib/librte_port/Makefile#n59
> ifeq ($(CONFIG_RTE_LIBRTE_KNI),y)
> SRCS-$(CONFIG_RTE_LIBRTE_PORT) += rte_port_kni.c
> endif
>
> And CONFIG_RTE_LIBRTE_KNI must be disabled for 32-bit.
>



-- 
Rgds,
Nishant

      reply	other threads:[~2016-10-09  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 21:46 Nishant Verma
2016-10-07 23:15 ` Thomas Monjalon
2016-10-09  2:46   ` Nishant Verma [this message]

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=CAHhCjUEjwdZbetr-c2iE4zbQ3f023XoGDQSqgXrGbcteQ_DEAg@mail.gmail.com \
    --to=vnish11@gmail.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=users@dpdk.org \
    /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).