DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xie, WeiX" <weix.xie@intel.com>
To: "Hunt, David" <david.hunt@intel.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] l3fwd-power: make interrupt wakeup log	thread safe
Date: Mon, 2 Nov 2020 10:35:36 +0000
Message-ID: <58d2d7a22aa648d0ac385ca25f9e9984@intel.com> (raw)
In-Reply-To: <2151ec7a-8083-b4e0-41e2-18297a68d9c9@intel.com>

Tested-by: Zhang, XiX <xix.zhang@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@dpdk.org] On Behalf Of David Hunt
> Sent: Wednesday, October 7, 2020 11:06 PM
> To: Burakov, Anatoly <anatoly.burakov@intel.com>; dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@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@intel.com
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> > ---
> 
> 
> Makes sense. Thanks.
> 
> Acked-by: David Hunt <david.hunt@intel.com>
> 
> 
> 


  reply	other threads:[~2020-11-02 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 12:03 [dpdk-dev] [PATCH] " Anatoly Burakov
2020-10-02 12:07 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2020-10-07 15:06   ` David Hunt
2020-11-02 10:35     ` Xie, WeiX [this message]
2020-10-09  6:26   ` Xie, WeiX
2020-10-30 12:46     ` David Marchand
2020-11-02 10:46   ` David Marchand

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=58d2d7a22aa648d0ac385ca25f9e9984@intel.com \
    --to=weix.xie@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=reshma.pattan@intel.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git