DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: thomas.monjalon@6wind.com
Cc: pablo.de.lara.guarch@intel.com, dev@dpdk.org,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH v2 1/4] examples: enable performance-thread in examples build
Date: Wed, 29 Mar 2017 17:38:53 +0100	[thread overview]
Message-ID: <20170329163856.10932-2-bruce.richardson@intel.com> (raw)
In-Reply-To: <20170329163856.10932-1-bruce.richardson@intel.com>

The performance-thread example was not build by default in the make
examples build target. It will compile ok for x86_64 targets so add it to
the examples makefile list for that platform.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 examples/Makefile | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/examples/Makefile b/examples/Makefile
index da2bfdd..49b0703 100644
--- a/examples/Makefile
+++ b/examples/Makefile
@@ -78,6 +78,9 @@ DIRS-$(CONFIG_RTE_LIBRTE_LPM) += load_balancer
 DIRS-y += multi_process
 DIRS-y += netmap_compat/bridge
 DIRS-$(CONFIG_RTE_LIBRTE_REORDER) += packet_ordering
+ifeq ($(CONFIG_RTE_ARCH_X86_64),y)
+DIRS-y += performance-thread
+endif
 DIRS-$(CONFIG_RTE_LIBRTE_IEEE1588) += ptpclient
 DIRS-$(CONFIG_RTE_LIBRTE_METER) += qos_meter
 DIRS-$(CONFIG_RTE_LIBRTE_SCHED) += qos_sched
-- 
2.9.3

  reply	other threads:[~2017-03-29 16:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 14:04 [dpdk-dev] [PATCH 0/4] improve build coverage Bruce Richardson
2017-03-29 14:04 ` [dpdk-dev] [PATCH 1/4] examples: enable performance-thread in examples build Bruce Richardson
2017-03-29 14:04 ` [dpdk-dev] [PATCH 2/4] config: enable crypto scheduler PMD by default Bruce Richardson
2017-03-30 14:48   ` Zhang, Roy Fan
2017-03-29 14:04 ` [dpdk-dev] [PATCH 3/4] devtools: remove special case build for perf thread example Bruce Richardson
2017-03-29 14:04 ` [dpdk-dev] [PATCH 4/4] devtools: add autotest app to build script Bruce Richardson
2017-03-29 16:38 ` [dpdk-dev] [PATCH v2 0/4] improve build coverage Bruce Richardson
2017-03-29 16:38   ` Bruce Richardson [this message]
2017-03-30  7:45     ` [dpdk-dev] [PATCH v2 1/4] examples: enable performance-thread in examples build Declan Doherty
2017-03-29 16:38   ` [dpdk-dev] [PATCH v2 2/4] config: enable crypto scheduler PMD by default Bruce Richardson
2017-03-30  7:45     ` Declan Doherty
2017-03-29 16:38   ` [dpdk-dev] [PATCH v2 3/4] devtools: remove special case build for perf thread example Bruce Richardson
2017-03-30  7:46     ` Declan Doherty
2017-03-30 14:31     ` Thomas Monjalon
2017-03-30 15:30       ` Bruce Richardson
2017-03-30 20:38         ` Thomas Monjalon
2017-03-31  9:15           ` Bruce Richardson
2017-03-31  9:56             ` Thomas Monjalon
2017-03-29 16:38   ` [dpdk-dev] [PATCH v2 4/4] devtools: add autotest app to build script Bruce Richardson
2017-03-30  7:47     ` Declan Doherty
2017-03-30 14:36     ` Thomas Monjalon
2017-03-30 15:33       ` Bruce Richardson
2017-03-30 20:42         ` Thomas Monjalon
2017-04-04 13:03           ` Ferruh Yigit
2017-04-06 19:45   ` [dpdk-dev] [PATCH v2 0/4] improve build coverage Thomas Monjalon

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=20170329163856.10932-2-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).