DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiming Chen" <chenqiming_huawei@163.com>
To: "haiyue.wang@intel.com" <haiyue.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: fix probability of obtaining mailbox lock failure
Date: Thu, 9 Sep 2021 11:34:06 +0800 (GMT+08:00)	[thread overview]
Message-ID: <5e9c7595.cfa5.17bc89eaaa1.Coremail.chenqiming_huawei@163.com> (raw)
In-Reply-To: <BN8PR11MB3795C43E6FF3189120734135F7D59@BN8PR11MB3795.namprd11.prod.outlook.com>

This is a problem triggered by the existing network. I discovered it a long time ago. I use the link state as an example. 
It is not to say that it is a link state problem, but to show that ixgbevf does have such a probability problem. 
The current modification and repeated verification can indeed solve the problem. The specific root cause of the problem may not be analyzed. 
Since the mailbox itself has a reliability mechanism, why not use it here?I understand that the status of the vf mailbox is read from the register. 
If you repeatedly reset the pf, will the transient fail because the register value has not been initialized, and it will succeed later?

      reply	other threads:[~2021-09-09  3:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  8:40 [dpdk-dev] [PATCH] " Qiming Chen
2021-09-06  1:48 ` Wang, Haiyue
2021-09-06  2:22 ` [dpdk-dev] [PATCH v2] " Qiming Chen
2021-09-08  3:33   ` Wang, Haiyue
2021-09-09  1:56     ` Qiming Chen
2021-09-09  2:13       ` Wang, Haiyue
2021-09-09  2:55       ` Wang, Haiyue
2021-09-09  3:34         ` Qiming Chen [this message]

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=5e9c7595.cfa5.17bc89eaaa1.Coremail.chenqiming_huawei@163.com \
    --to=chenqiming_huawei@163.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=stable@dpdk.org \
    /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).