-----Original Message----- > Date: Fri, 12 Oct 2018 10:24:16 +0800 > From: Chao Zhu <chao...@linux.vnet.ibm.com> > To: 'Jerin Jacob' <jerin.ja...@caviumnetworks.com> > CC: dev@dpdk.org, tho...@monjalon.net, gowrishanka...@linux.vnet.ibm.com, > ola.liljed...@arm.com > Subject: 答复: [dpdk-dev] [PATCH] eal/ppc64: add support for rte pause > X-Mailer: Microsoft Outlook 16.0 > > > -----邮件原件----- > 发件人: Jerin Jacob <jerin.ja...@caviumnetworks.com> > 发送时间: 2018年10月7日 14:19 > 收件人: Chao Zhu <chao...@linux.vnet.ibm.com> > 抄送: dev@dpdk.org; tho...@monjalon.net; gowrishanka...@linux.vnet.ibm.com; > ola.liljed...@arm.com; Jerin Jacob <jerin.ja...@caviumnetworks.com> > 主题: [dpdk-dev] [PATCH] eal/ppc64: add support for rte pause > > Add support for rte_pause() implementation for ppc64. > > Signed-off-by: Jerin Jacob <jerin.ja...@caviumnetworks.com> > --- > > The reference implementation for Linux's cpu_relax() for ppc64 is at > https://elixir.bootlin.com/linux/latest/source/arch/powerpc/include/asm/proc > essor.h#L440 > > --- > lib/librte_eal/common/include/arch/ppc_64/rte_pause.h | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/lib/librte_eal/common/include/arch/ppc_64/rte_pause.h > b/lib/librte_eal/common/include/arch/ppc_64/rte_pause.h > index 8bd835764..16e47ce22 100644 > --- a/lib/librte_eal/common/include/arch/ppc_64/rte_pause.h > +++ b/lib/librte_eal/common/include/arch/ppc_64/rte_pause.h > @@ -9,10 +9,17 @@ > extern "C" { > #endif > > +#include "rte_atomic.h" > + > #include "generic/rte_pause.h" > > static inline void rte_pause(void) > { > + /* Set hardware multi-threading low priority */ > + asm volatile("or 1,1,1"); > + /* Set hardware multi-threading medium priority */ > + asm volatile("or 2,2,2"); > + rte_compiler_barrier(); > } > > #ifdef __cplusplus > -- > 2.19.0 > > Acked-by: Chao Zhu <chao...@linux.vnet.ibm.com>
Thomas, Just noticed, due to some reason, The above Acked-by: is not reflected in patchwork. http://patches.dpdk.org/patch/46195/ Probably because, it was not a "inline" reply which patchwork couldn't parse it. > >