From: David Marchand <david.marchand@redhat.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"Wei Zhao" <wei.zhao1@intel.com>, "Jeff Guo" <jia.guo@intel.com>,
dev <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/4] net/ixgbe: add support for aarch32
Date: Tue, 23 Jun 2020 10:37:12 +0200 [thread overview]
Message-ID: <CAJFAV8ytmrWfeqWhcjG82G_TpHzb52ufGXUSig=Gik-UH--4SQ@mail.gmail.com> (raw)
In-Reply-To: <20200623065856.41189-3-ruifeng.wang@arm.com>
Hello Ruifeng,
On Tue, Jun 23, 2020 at 9:00 AM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
> diff --git a/config/defconfig_arm-armv7a-linuxapp-gcc b/config/defconfig_arm-armv7a-linuxapp-gcc
> index 9ecc2a526..9c6d387cf 100644
> --- a/config/defconfig_arm-armv7a-linuxapp-gcc
> +++ b/config/defconfig_arm-armv7a-linuxapp-gcc
> @@ -30,6 +30,7 @@ CONFIG_RTE_LIBRTE_EAL_VMWARE_TSC_MAP_SUPPORT=n
> # KNI is not supported on 32-bit
> CONFIG_RTE_LIBRTE_KNI=n
>
> +CONFIG_RTE_LIBRTE_IXGBE_PMD=y
All components are enabled by default in the common_base file.
We explicitly disable components in the targets config files that
can't support them.
$ git grep IXGBE_PMD= origin/master -- config/
config/common_base:CONFIG_RTE_LIBRTE_IXGBE_PMD=y
config/defconfig_arm-armv7a-linuxapp-gcc:CONFIG_RTE_LIBRTE_IXGBE_PMD=n
config/defconfig_ppc_64-power8-linuxapp-gcc:CONFIG_RTE_LIBRTE_IXGBE_PMD=n
> # cannot use those on ARM
> CONFIG_RTE_LIBRTE_ARK_PMD=n
> CONFIG_RTE_LIBRTE_EM_PMD=n
> @@ -39,7 +40,6 @@ CONFIG_RTE_LIBRTE_E1000_PMD=n
> CONFIG_RTE_LIBRTE_ENIC_PMD=n
> CONFIG_RTE_LIBRTE_FM10K_PMD=n
> CONFIG_RTE_LIBRTE_I40E_PMD=n
> -CONFIG_RTE_LIBRTE_IXGBE_PMD=n
So removing this line only should be enough.
Idem with i40e in following patch.
> CONFIG_RTE_LIBRTE_VMXNET3_PMD=n
> CONFIG_RTE_LIBRTE_QEDE_PMD=n
> CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n
--
David Marchand
next prev parent reply other threads:[~2020-06-23 8:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 6:50 [dpdk-dev] [PATCH 0/3] aarch32 compilation Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 1/3] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-05-01 14:55 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-04-24 6:50 ` [dpdk-dev] [PATCH 2/3] net/ixgbe: add support " Ruifeng Wang
2020-05-01 14:59 ` Ferruh Yigit
2020-05-06 7:54 ` Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 3/3] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-05-01 15:06 ` [dpdk-dev] [PATCH 0/3] aarch32 compilation Ferruh Yigit
2020-05-06 8:09 ` Ruifeng Wang
2020-05-06 10:14 ` Ferruh Yigit
2020-05-06 13:54 ` Ruifeng Wang
2020-05-06 14:14 ` Ferruh Yigit
2020-05-06 14:36 ` Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 0/4] " Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-23 8:37 ` David Marchand [this message]
2020-06-23 8:59 ` Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-26 13:44 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ferruh Yigit
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='CAJFAV8ytmrWfeqWhcjG82G_TpHzb52ufGXUSig=Gik-UH--4SQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jia.guo@intel.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=wei.zhao1@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).