Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-11-02 Thread David Marchand
On Fri, Oct 2, 2020 at 2:07 PM Anatoly Burakov wrote: > > Currently, the interrupt status notification prevents log spam by > remembering whether previous interrupt wakeup was due to traffic or due > to timeout expiring. However, it is a single variable that can > potentially be accessed from mult

Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-11-02 Thread Xie, WeiX
11:06 PM > To: Burakov, Anatoly ; dev@dpdk.org > Cc: Pattan, Reshma > Subject: Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log > thread safe > > Hi Anatoly, > > On 2/10/2020 1:07 PM, Anatoly Burakov wrote: > > Currently, the interrupt status notification

Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-10-30 Thread David Marchand
On Fri, Oct 9, 2020 at 8:27 AM Xie, WeiX wrote: > > Tested-by: Zhang, XiX A bit surprised to read a Tested-by: token sent for someone else. Is this a typo? Besides, it should be "Xi Zhang", no comma. -- David Marchand

Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-10-08 Thread Xie, WeiX
Tested-by: Zhang, XiX > -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Anatoly Burakov > Sent: Friday, October 2, 2020 8:07 PM > To: dev@dpdk.org > Cc: Hunt, David ; Pattan, Reshma > ; Burakov, Anatoly > Subject: [dpdk-dev] [PATCH

Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-10-07 Thread David Hunt
Hi Anatoly, On 2/10/2020 1:07 PM, Anatoly Burakov wrote: Currently, the interrupt status notification prevents log spam by remembering whether previous interrupt wakeup was due to traffic or due to timeout expiring. However, it is a single variable that can potentially be accessed from multiple

[dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe

2020-10-02 Thread Anatoly Burakov
Currently, the interrupt status notification prevents log spam by remembering whether previous interrupt wakeup was due to traffic or due to timeout expiring. However, it is a single variable that can potentially be accessed from multiple threads, so it is not thread-safe. Fix it by having per-lco