From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Amr Mokhtar <amr.mokhtar@intel.com>, dev@dpdk.org
Cc: niall.power@intel.com, chris.macnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v1 6/6] bbdev: auxiliary changes to DPDK framework
Date: Wed, 4 Oct 2017 17:14:23 +0100 [thread overview]
Message-ID: <dcb14ca4-e35e-292a-3dda-aa58db35f45f@intel.com> (raw)
In-Reply-To: <1506735475-77078-6-git-send-email-amr.mokhtar@intel.com>
On 30-Sep-17 2:37 AM, Amr Mokhtar wrote:
> diff --git a/mk/rte.app.mk b/mk/rte.app.mk
> index c25fdd9..7286ad9 100644
> --- a/mk/rte.app.mk
> +++ b/mk/rte.app.mk
> @@ -93,6 +93,7 @@ _LDLIBS-$(CONFIG_RTE_LIBRTE_NET) += -lrte_net
> _LDLIBS-$(CONFIG_RTE_LIBRTE_ETHER) += -lrte_ethdev
> _LDLIBS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += -lrte_cryptodev
> _LDLIBS-$(CONFIG_RTE_LIBRTE_EVENTDEV) += -lrte_eventdev
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_BBDEV) += -lrte_bbdev
> _LDLIBS-$(CONFIG_RTE_LIBRTE_MEMPOOL) += -lrte_mempool
> _LDLIBS-$(CONFIG_RTE_DRIVER_MEMPOOL_RING) += -lrte_mempool_ring
> _LDLIBS-$(CONFIG_RTE_LIBRTE_RING) += -lrte_ring
> @@ -146,6 +147,18 @@ endif # $(CONFIG_RTE_LIBRTE_VHOST)
> _LDLIBS-$(CONFIG_RTE_LIBRTE_VMXNET3_PMD) += -lrte_pmd_vmxnet3_uio
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_XENVIRT) += -lrte_pmd_xenvirt -lxenstore
>
> +ifeq ($(CONFIG_RTE_LIBRTE_BBDEV),y)
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_NULL) += -lrte_pmd_bbdev_null
> +
> +# TURBO SOFTWARE PMD is dependent on the BBLIB library
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -lrte_pmd_bbdev_turbo_sw
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -L$(BBLIB_PATH)/lib_common -lcommon
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -L$(BBLIB_PATH)/lib_crc -lcrc
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -L$(BBLIB_PATH)/lib_turbo -lturbo
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -L$(BBLIB_PATH)/lib_rate_matching -lrate_matching
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += -lirc -limf -lstdc++ -lipps
> +endif # CONFIG_RTE_LIBRTE_BBDEV
> +
> ifeq ($(CONFIG_RTE_LIBRTE_CRYPTODEV),y)
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_AESNI_MB) += -lrte_pmd_aesni_mb
> _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_AESNI_MB) += -L$(AESNI_MULTI_BUFFER_LIB_PATH) -lIPSec_MB
>
Changes to makefiles should probably go in with the patches that
introduce the libraries. As it stands, if something breaks the build
inside one of the PMD's or BBDEV itself (which is the case right now),
we won't know about it until this patch.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2017-10-04 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 1:37 [dpdk-dev] [PATCH v1 1/6] bbdev: librte_bbdev library Amr Mokhtar
2017-09-30 1:37 ` [dpdk-dev] [PATCH v1 2/6] bbdev: PMD drivers (null/turbo_sw) Amr Mokhtar
2017-09-30 1:37 ` [dpdk-dev] [PATCH v1 3/6] bbdev: test applications Amr Mokhtar
2017-09-30 1:37 ` [dpdk-dev] [PATCH v1 4/6] bbdev: sample app Amr Mokhtar
2017-09-30 1:37 ` [dpdk-dev] [PATCH v1 5/6] bbdev: documentation Amr Mokhtar
2017-09-30 1:37 ` [dpdk-dev] [PATCH v1 6/6] bbdev: auxiliary changes to DPDK framework Amr Mokhtar
2017-10-04 16:14 ` Burakov, Anatoly [this message]
2017-10-16 9:00 ` Mokhtar, Amr
2017-10-16 10:03 ` [dpdk-dev] [PATCH v1 1/6] bbdev: librte_bbdev library De Lara Guarch, Pablo
2017-10-18 2:25 ` Mokhtar, Amr
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=dcb14ca4-e35e-292a-3dda-aa58db35f45f@intel.com \
--to=anatoly.burakov@intel.com \
--cc=amr.mokhtar@intel.com \
--cc=chris.macnamara@intel.com \
--cc=dev@dpdk.org \
--cc=niall.power@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).