From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: neeraj kumar <neeraj2290@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH]: to create KNI on 32 bit system
Date: Mon, 27 Jan 2014 16:07:32 +0100 [thread overview]
Message-ID: <201401271607.32427.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CAAb4JzGs4PREfHpepDSd-H50FvNDRRjONyxs8JnPVHHpKuWNsw@mail.gmail.com>
Hello,
16/01/2014 07:59, neeraj kumar:
> It is in regard to this commit *d92c66f5ac53a7b803efcb4782e601ea99c38a7e*
>
> By default in 32 bit kernel *High Memory Support* option of make menuconfig
> is selected with size 4 GB, therefore it gives compilation error.
>
> Thus to use KNI on 32 bit system we need kernel with High memory support of
> 64 GB, i.e *PAE* (*Physical Address Extension*) *Support*, then we can be
> able to use it in 32 bit environment.
So KNI can be enabled on 32-bit system only if PAE is enabled.
Then we should either disable it by default, or use a kconfig trick to check
PAE before building.
> #
> # Compile librte_kni
> -# KNI is not supported on 32-bit
> +# KNI will be supported on 32-bit if
> +# PAE(Physical Address Extension, i.e High page support)
> +# is configured in the kernel
> #
OK
> -CONFIG_RTE_LIBRTE_KNI=n
> +CONFIG_RTE_LIBRTE_KNI=y
It can be applied only if PAE is checked when building.
> *PATCH 3: Kernel config change*
> --- a/.config 2014-01-06 15:57:24.549042056 +0530
> +++ b/.config 2014-01-06 15:58:03.263773338 +0530
This patch cannot be applied to DPDK.
Please try to send your patch with git as described here:
http://dpdk.org/dev#send
Thanks
--
Thomas
prev parent reply other threads:[~2014-01-27 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 6:59 neeraj kumar
2014-01-27 15:07 ` Thomas Monjalon [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=201401271607.32427.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=neeraj2290@gmail.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).