From: "Betts, Ian" <ian.betts@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v9 3/4] examples: add l3fwd-thread example in performance-thread
Date: Tue, 8 Dec 2015 01:54:21 +0000 [thread overview]
Message-ID: <877C1F8553E92F43898365570816082F35C0C401@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1915132.14VGSMCEh2@xps13>
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Tuesday, December 8, 2015 1:36 AM
To: Betts, Ian
Cc: dev@dpdk.org; stephen@networkplumber.org; Richardson, Bruce
Subject: Re: [PATCH v9 3/4] examples: add l3fwd-thread example in performance-thread
> +M: Ian Betts <ian.betts@intel.com>
> +M: John McNamara <john.mcnamara@intel.com>
> +F: doc/guides/sample_app_ug/performance_thread.rst
> Why doing 2 sections?
> John is already the doc maintainer. You don't need to add him here.
I just copy most of the other examples which also do this.
I also thought it was odd.
I will remove him.
> --- a/examples/Makefile
> +++ b/examples/Makefile
> @@ -77,5 +77,9 @@ DIRS-y += vmdq
> DIRS-y += vmdq_dcb
> DIRS-$(CONFIG_RTE_LIBRTE_POWER) += vm_power_manager
> DIRS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += l2fwd-crypto
> -
> +ifneq ($(CONFIG_RTE_EXEC_ENV_LINUXAPP),)
> +ifneq ($(CONFIG_RTE_ARCH_X86_64),)
> +DIRS-y += performance-thread
> +endif
> +endif
> Matter of taste, I would prefer DIRS-$(CONFIG_RTE_ARCH_X86_64)
I need to combine CONFIG_RTE_EXEC_ENV_LINUXAPP ( the two clauses )
next prev parent reply other threads:[~2015-12-08 1:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 16:21 [dpdk-dev] [PATCH v7 0/4] examples: add performance-thread Ian Betts
2015-12-03 16:21 ` [dpdk-dev] [PATCH v7 1/4] doc: add sample application guide for performance-thread Ian Betts
2015-12-03 16:21 ` [dpdk-dev] [PATCH v7 2/4] examples: add lthread subsystem " Ian Betts
2015-12-04 10:34 ` [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread Ian Betts
2015-12-04 10:34 ` [dpdk-dev] [PATCH v8 1/4] doc: add sample application guide for performance-thread Ian Betts
2015-12-07 17:58 ` [dpdk-dev] [PATCH v9 0/4] examples: add performance-thread Ian Betts
2015-12-07 17:58 ` [dpdk-dev] [PATCH v9 1/4] doc: add sample application guide for performance-thread Ian Betts
2015-12-07 17:58 ` [dpdk-dev] [PATCH v9 2/4] examples: add lthread subsystem " Ian Betts
2015-12-07 17:58 ` [dpdk-dev] [PATCH v9 3/4] examples: add l3fwd-thread example in performance-thread Ian Betts
2015-12-08 1:35 ` Thomas Monjalon
2015-12-08 1:54 ` Betts, Ian [this message]
2015-12-08 2:28 ` Thomas Monjalon
2015-12-08 1:39 ` Thomas Monjalon
2015-12-07 17:58 ` [dpdk-dev] [PATCH v9 4/4] examples: add pthread_shim example to performance thread Ian Betts
2015-12-04 10:34 ` [dpdk-dev] [PATCH v8 2/4] examples: add lthread subsystem forperformance-thread Ian Betts
2015-12-07 2:38 ` Thomas Monjalon
2015-12-04 10:34 ` [dpdk-dev] [PATCH v8 3/4] examples: add l3fwd-thread example in performance-thread Ian Betts
2015-12-07 2:36 ` Thomas Monjalon
2015-12-07 4:46 ` Betts, Ian
2015-12-07 11:20 ` Thomas Monjalon
2015-12-04 10:34 ` [dpdk-dev] [PATCH v8 4/4] examples: add pthread_shim example to performance thread Ian Betts
2015-12-04 11:21 ` [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread Kulasek, TomaszX
2015-12-04 18:03 ` Stephen Hemminger
2015-12-04 18:33 ` Thomas Monjalon
2015-12-05 12:06 ` Betts, Ian
2015-12-05 17:53 ` Glynn, Michael J
2015-12-05 19:47 ` Stephen Hemminger
2015-12-05 21:21 ` Thomas Monjalon
2015-12-06 6:17 ` Betts, Ian
2015-12-04 22:10 ` Betts, Ian
2015-12-03 16:21 ` [dpdk-dev] [PATCH v7 3/4] examples: add l3fwd-thread example in performance-thread Ian Betts
2015-12-03 16:21 ` [dpdk-dev] [PATCH v7 4/4] examples: add pthread_shim example to performance thread Ian Betts
2015-12-03 16:44 ` [dpdk-dev] [PATCH v7 0/4] examples: add performance-thread Kulasek, TomaszX
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=877C1F8553E92F43898365570816082F35C0C401@IRSMSX103.ger.corp.intel.com \
--to=ian.betts@intel.com \
--cc=dev@dpdk.org \
--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).