From: Bruce Richardson <bruce.richardson@intel.com>
To: Rasesh Mody <rasesh.mody@qlogic.com>
Cc: thomas.monjalon@6wind.com, dev@dpdk.org, ameen.rahman@qlogic.com,
harish.patil@qlogic.com, sony.chacko@qlogic.com
Subject: Re: [dpdk-dev] [PATCH v3 10/10] qede: Enable PMD build
Date: Tue, 22 Mar 2016 11:21:44 +0000 [thread overview]
Message-ID: <20160322112144.GE19248@bricha3-MOBL3> (raw)
In-Reply-To: <1458348805-32648-11-git-send-email-rasesh.mody@qlogic.com>
On Fri, Mar 18, 2016 at 05:53:25PM -0700, Rasesh Mody wrote:
> Signed-off-by: Harish Patil <harish.patil@qlogic.com>
> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
> ---
> config/common_base | 14 ++++++++++++++
> drivers/net/Makefile | 1 +
> mk/rte.app.mk | 2 ++
> scripts/test-build.sh | 1 +
> 4 files changed, 18 insertions(+)
>
> diff --git a/config/common_base b/config/common_base
> index dbd405b..14b37df 100644
> --- a/config/common_base
> +++ b/config/common_base
> @@ -295,6 +295,20 @@ CONFIG_RTE_LIBRTE_PMD_BOND=y
> CONFIG_RTE_LIBRTE_BOND_DEBUG_ALB=n
> CONFIG_RTE_LIBRTE_BOND_DEBUG_ALB_L1=n
>
> +# QLogic 25G/40G PMD
> +#
> +CONFIG_RTE_LIBRTE_QEDE_PMD=y
> +CONFIG_RTE_LIBRTE_QEDE_DEBUG_INIT=n
> +CONFIG_RTE_LIBRTE_QEDE_DEBUG_INFO=n
> +CONFIG_RTE_LIBRTE_QEDE_DEBUG_ECORE=n
> +CONFIG_RTE_LIBRTE_QEDE_DEBUG_TX=n
> +CONFIG_RTE_LIBRTE_QEDE_DEBUG_RX=n
> +CONFIG_RTE_LIBRTE_QEDE_RX_COAL_US=24
> +CONFIG_RTE_LIBRTE_QEDE_TX_COAL_US=48
> +CONFIG_RTE_LIBRTE_QEDE_TX_SWITCHING=y
> +#Provides path/name of the firmware file
> +CONFIG_RTE_LIBRTE_QEDE_FW=n
> +
> #
> # Compile software PMD backed by AF_PACKET sockets (Linux only)
> #
> diff --git a/drivers/net/Makefile b/drivers/net/Makefile
> index 0c3393f..61d3f16 100644
> --- a/drivers/net/Makefile
> +++ b/drivers/net/Makefile
> @@ -51,5 +51,6 @@ DIRS-$(CONFIG_RTE_LIBRTE_PMD_SZEDATA2) += szedata2
> DIRS-$(CONFIG_RTE_LIBRTE_VIRTIO_PMD) += virtio
> DIRS-$(CONFIG_RTE_LIBRTE_VMXNET3_PMD) += vmxnet3
> DIRS-$(CONFIG_RTE_LIBRTE_PMD_XENVIRT) += xenvirt
> +DIRS-$(CONFIG_RTE_LIBRTE_QEDE_PMD) += qede
In general, lists in DPDK, including this list of subdirectories in the makefile
are kept in alphabetical order, rather than just having new items appended at the
end.
/Bruce
>
> include $(RTE_SDK)/mk/rte.subdir.mk
> diff --git a/mk/rte.app.mk b/mk/rte.app.mk
> index a1cd9a3..9bb2264 100644
> --- a/mk/rte.app.mk
> +++ b/mk/rte.app.mk
> @@ -101,6 +101,7 @@ _LDLIBS-$(CONFIG_RTE_LIBRTE_MLX5_PMD) += -libverbs
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_SZEDATA2) += -lsze2
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_XENVIRT) += -lxenstore
> _LDLIBS-$(CONFIG_RTE_LIBRTE_MPIPE_PMD) += -lgxio
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_QEDE_PMD) += -lz
> # QAT / AESNI GCM PMDs are dependent on libcrypto (from openssl)
> # for calculating HMAC precomputes
> ifeq ($(CONFIG_RTE_LIBRTE_PMD_QAT),y)
> @@ -146,6 +147,7 @@ _LDLIBS-$(CONFIG_RTE_LIBRTE_MPIPE_PMD) += -lrte_pmd_mpipe
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_RING) += -lrte_pmd_ring
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_PCAP) += -lrte_pmd_pcap
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_AF_PACKET) += -lrte_pmd_af_packet
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_QEDE_PMD) += -lrte_pmd_qede
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_NULL) += -lrte_pmd_null
>
> ifeq ($(CONFIG_RTE_LIBRTE_CRYPTODEV),y)
> diff --git a/scripts/test-build.sh b/scripts/test-build.sh
> index 5f3cab5..dfc8915 100755
> --- a/scripts/test-build.sh
> +++ b/scripts/test-build.sh
> @@ -116,6 +116,7 @@ config () # <directory> <target> <options>
> test "$DPDK_DEP_ZLIB" != y || \
> sed -ri 's,(BNX2X_PMD=)n,\1y,' $1/.config
> sed -ri 's,(NFP_PMD=)n,\1y,' $1/.config
> + sed -ri 's,(QEDE_PMD=)n,\1y,' $1/.config
> test "$DPDK_DEP_PCAP" != y || \
> sed -ri 's,(PCAP=)n,\1y,' $1/.config
> test -z "$AESNI_MULTI_BUFFER_LIB_PATH" || \
> --
> 1.7.10.3
>
next prev parent reply other threads:[~2016-03-22 11:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 0:53 [dpdk-dev] [PATCH v3 00/10] qede: Add qede PMD Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 01/10] qede: Add maintainers Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 02/10] qede: Add documentation Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 03/10] qede: Add license file Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 04/10] qede: Add base driver Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 05/10] qede: Add core driver Rasesh Mody
2016-03-21 17:32 ` Stephen Hemminger
2016-03-22 1:14 ` Rasesh Mody
2016-03-22 10:55 ` Bruce Richardson
2016-03-22 11:03 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 06/10] qede: Add L2 support Rasesh Mody
2016-03-22 11:04 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 07/10] qede: Add SRIOV support Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 08/10] qede: Add attention support Rasesh Mody
2016-03-22 11:07 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 09/10] qede: Add DCBX support Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 10/10] qede: Enable PMD build Rasesh Mody
2016-03-22 11:21 ` Bruce Richardson [this message]
2016-03-22 11:21 ` [dpdk-dev] [PATCH v3 00/10] qede: Add qede PMD Richardson, Bruce
2016-03-22 11:30 ` Bruce Richardson
2016-03-29 20:52 ` Rasesh Mody
2016-03-30 12:34 ` Bruce Richardson
2016-03-24 1:52 ` Rasesh Mody
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=20160322112144.GE19248@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=ameen.rahman@qlogic.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=rasesh.mody@qlogic.com \
--cc=sony.chacko@qlogic.com \
--cc=thomas.monjalon@6wind.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).