From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: dev@dpdk.org, Chao Zhu <chaozhu@linux.vnet.ibm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
pradeep@us.ibm.com
Subject: Re: [dpdk-dev] [PATCH 1/6] config: enable lpm, port, table, pipeline, acl, sched libraries for ppc64le
Date: Sat, 09 Jul 2016 22:53:19 +0200 [thread overview]
Message-ID: <13354717.T3ZIX32DYy@xps13> (raw)
In-Reply-To: <57810C81.90807@linux.vnet.ibm.com>
2016-07-09 20:08, gowrishankar:
> Hi Thomas,
>
> On Friday 08 July 2016 06:27 PM, Thomas Monjalon wrote:
> > The comment and these lines can be removed and rely on default
> > enabling in config/common_base. I suggest to enable (remove disabling)
> > a feature at a time in the patch fixing the feature for PPC.
>
> Sure. So, do you suggest to send individual patchset (or patch) for each
> feature being enabled, one by one ?.
No, my comment was about dropping the patch #1 and update following patches.
Example: in the patch fixing LPM, you can remove the line disabling LPM
in the config file.
next prev parent reply other threads:[~2016-07-09 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 2:57 [dpdk-dev] [PATCH 0/6] enable lpm, acl and other missing libraries in ppc64le Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 1/6] config: enable lpm, port, table, pipeline, acl, sched libraries for ppc64le Gowrishankar
2016-07-08 12:57 ` Thomas Monjalon
2016-07-09 14:38 ` gowrishankar
2016-07-09 20:53 ` Thomas Monjalon [this message]
2016-07-07 2:57 ` [dpdk-dev] [PATCH 2/6] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 3/6] acl: add altivec intrinsics for dpdk acl " Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 4/6] table: cache align rte_bucket_4_8 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 5/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 6/6] l3fwd: add altivec support for em_hash_key Gowrishankar
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 2:56 [dpdk-dev] [PATCH 1/6] config: enable lpm, port, table, pipeline, acl, sched libraries for ppc64le Gowrishankar
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=13354717.T3ZIX32DYy@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=konstantin.ananyev@intel.com \
--cc=pradeep@us.ibm.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).