From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: gowrishankar muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
dev@dpdk.org, Chao Zhu <chaozhu@linux.vnet.ibm.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Pradeep <pradeep@us.ibm.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v7 0/9] enable lpm, acl and other missing libraries in ppc64le
Date: Tue, 27 Sep 2016 15:01:53 +0800 [thread overview]
Message-ID: <20160927070153.GJ25823@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <d7961f5c-2a44-56c1-8786-d3063add0342@linux.vnet.ibm.com>
On Tue, Sep 27, 2016 at 12:16:32PM +0530, gowrishankar muthukrishnan wrote:
> On Friday 09 September 2016 09:29 PM, Thomas Monjalon wrote:
> >>>v7 changes:
> >>>- removed enforcing cache alignment for table hash structs and
> >>> instead check only for multiples of 64 bytes.
> >>>
> >>Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> >Applied, thanks
> >
> >We now have some AltiVec code in DPDK!
> >
> >
> Thank you Thomas, could this also go into stable tree ? (Added
> stable@dpdk.org in CC).
This patchset is more like enabling DPDK on a new platform, so, it's
a new feature to me, which is not a good candidate for a stable release:
the basic rule of it is only bug fixing patches are allowed.
The reason I picked "examples/ip_pipeline: fix lcore mapping for ppc64"
to stable branch is it looks like a bug fixing patch to me, while others
are not. OTOH, it also looks like a PPC enabling patch to me; from this
point of view, I may need drop it.
IBM guys, does it make sense to pick that one only to stable branch?
Or, should I drop it?
Thanks.
--yliu
prev parent reply other threads:[~2016-09-27 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 16:48 [PATCH v7 0/9] enable lpm, acl and other missing libraries in ppc64le Gowrishankar
2016-09-08 16:48 ` [PATCH v7 1/9] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar
2016-09-08 16:48 ` [PATCH v7 2/9] acl: add altivec intrinsics for dpdk acl " Gowrishankar
2016-09-08 16:48 ` [PATCH v7 3/9] l3fwd: add altivec support for em_hash_key Gowrishankar
2016-09-08 16:48 ` [PATCH v7 4/9] table: enable table library for ppc64le Gowrishankar
2016-09-08 16:48 ` [PATCH v7 5/9] sched: enable sched " Gowrishankar
2016-09-08 16:48 ` [PATCH v7 6/9] port: enable port " Gowrishankar
2016-09-08 16:48 ` [PATCH v7 7/9] pipeline: enable pipeline " Gowrishankar
2016-09-08 16:48 ` [PATCH v7 8/9] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar
2016-09-08 16:48 ` [PATCH v7 9/9] table: fix verification on hash bucket header alignment Gowrishankar
2016-09-08 16:54 ` [PATCH v7 0/9] enable lpm, acl and other missing libraries in ppc64le Dumitrescu, Cristian
2016-09-09 15:59 ` Thomas Monjalon
2016-09-27 6:46 ` gowrishankar muthukrishnan
2016-09-27 7:01 ` Yuanhan Liu [this message]
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=20160927070153.GJ25823@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.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 \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.