DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: wangyunjian <wangyunjian@huawei.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: xudingke <xudingke@huawei.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Lilijun (Jerry, Cloud Networking)" <jerry.lilijun@huawei.com>,
	"Zhang, Jerry" <jerry.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix crash when	calling	i40e_vsi_delete_mac
Date: Tue, 23 Apr 2019 03:39:10 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115336E6A6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <34EFBCA9F01B0748BEB6B629CE643AE60CAACBA7@DGGEMM533-MBX.china.huawei.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of wangyunjian
> Sent: Tuesday, April 16, 2019 10:05 AM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; dev@dpdk.org
> Cc: xudingke <xudingke@huawei.com>; stable@dpdk.org; Lilijun (Jerry,
> Cloud Networking) <jerry.lilijun@huawei.com>; Zhang, Jerry
> <jerry.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix crash when calling
> i40e_vsi_delete_mac
> 
> >
> > That is not specific to i40e or macvlan filter.
> > If inside your app several threads concurrently access/modify NIC
> > config, then you need to provide some synchronization mechanism for
> them.
> > DPDK ethdev API (as most others) on itself doesn't provide any
> > synchronization, leaving it up to the upper layer to choose the most
> > appropriate one.
> > Konstantin
> 
> Thanks. Now the lsc thread isn't controled by the upper layer.
> Do you have any idea to fix it?

What do you mean "the lsc thread isn't controlled by the upper layer"?

you may invoke ethdev APIs in LSC callback function, and use some lock to prevent race condition,

> 
> Thanks,
> Yunjian

  parent reply	other threads:[~2019-04-23  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13  9:54 wangyunjian
2019-04-13  9:54 ` wangyunjian
2019-04-15 12:21 ` Ananyev, Konstantin
2019-04-15 12:21   ` Ananyev, Konstantin
2019-04-15 12:50   ` Zhang, Qi Z
2019-04-15 12:50     ` Zhang, Qi Z
2019-04-16  2:05   ` wangyunjian
2019-04-16  2:05     ` wangyunjian
2019-04-23  3:39     ` Zhang, Qi Z [this message]
2019-04-23  3:39       ` Zhang, Qi Z

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=039ED4275CED7440929022BC67E706115336E6A6@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=jerry.zhang@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=stable@dpdk.org \
    --cc=wangyunjian@huawei.com \
    --cc=xudingke@huawei.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).