[dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log thread safe
Xie, WeiX
weix.xie at intel.com
Mon Nov 2 11:35:36 CET 2020
Tested-by: Zhang, XiX <xix.zhang at intel.com>
The tag is correct and I send the email on behalf of him, his mailbox can't receive dev patch. Thx.
Regards,
Xie Wei
> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Hunt
> Sent: Wednesday, October 7, 2020 11:06 PM
> To: Burakov, Anatoly <anatoly.burakov at intel.com>; dev at dpdk.org
> Cc: Pattan, Reshma <reshma.pattan at intel.com>
> 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 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-lcore interrupt status.
> >
> > Fixes: f4d1e19c293d ("examples/l3fwd-power: add Rx interrupt timeout")
> > Cc: anatoly.burakov at intel.com
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov at intel.com>
> > ---
>
>
> Makes sense. Thanks.
>
> Acked-by: David Hunt <david.hunt at intel.com>
>
>
>
More information about the dev
mailing list