Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-25 Thread Thomas Monjalon
25/04/2020 17:51, Phil Yang: > From: Thomas Monjalon > > 20/04/2020 18:05, Phil Yang: > > > This patch depends on patch: > > > http://patchwork.dpdk.org/patch/65997/ > > > > In order to ease patch tracking, you should have kept the first patch > > in the next version of your series. We don't spli

Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-25 Thread Phil Yang
Honnappa Nagarahalli > ; Gavin Hu ; nd > ; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update > > 20/04/2020 18:05, Phil Yang: > > This patch depends on patch: > > http://patchwork.dpdk.org/patch/65997/ > > In order to ease pat

Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-25 Thread Thomas Monjalon
20/04/2020 18:05, Phil Yang: > This patch depends on patch: > http://patchwork.dpdk.org/patch/65997/ In order to ease patch tracking, you should have kept the first patch in the next version of your series. We don't split series in general.

Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-24 Thread Phil Yang
> -Original Message- > From: Carrillo, Erik G > Sent: Friday, April 24, 2020 9:27 AM > To: Honnappa Nagarahalli ; Phil Yang > ; rsanf...@akamai.com; dev@dpdk.org > Cc: tho...@monjalon.net; david.march...@redhat.com; Ananyev, > Konstantin ; jer...@marvell.com; > hemant.agra...@nxp.com; Gavi

Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-23 Thread Carrillo, Erik G
Hi Honnappa, > -Original Message- > From: Honnappa Nagarahalli > Sent: Thursday, April 23, 2020 3:06 PM > To: Phil Yang ; Carrillo, Erik G > ; rsanf...@akamai.com; dev@dpdk.org > Cc: tho...@monjalon.net; david.march...@redhat.com; Ananyev, > Konstantin ; jer...@marvell.com; > hemant.agra.

Re: [dpdk-dev] [PATCH v2] lib/timer: relax barrier for status update

2020-04-23 Thread Honnappa Nagarahalli
Hi Erik, > Subject: [PATCH v2] lib/timer: relax barrier for status update > > Volatile has no ordering semantics. The rte_timer structure defines timer > status as a volatile variable and uses the rte_r/wmb barrier to guarantee > inter-thread visibility. > > This patch optimized the volatile ope