patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wang, Liang-min" <liang-min.wang@intel.com>,
	"daniels@research.att.com" <daniels@research.att.com>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/ixgbevf: add an option pflink_fullchk to get link status nowait
Date: Tue, 11 Jun 2019 01:29:02 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115339A0DD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1559922981-101848-1-git-send-email-haiyue.wang@intel.com>



> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Monday, June 10, 2019 7:17 PM
> To: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>; Wang, Liang-min <liang-min.wang@intel.com>;
> daniels@research.att.com; ktraynor@redhat.com
> Cc: stable@dpdk.org
> Subject: RE: [PATCH v2] net/ixgbevf: add an option pflink_fullchk to get link
> status nowait
> 
> 
> 
> > -----Original Message-----
> > From: Wang, Haiyue
> > Sent: Friday, June 7, 2019 11:56 PM
> > To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo
> > <wenzhuo.lu@intel.com>; Wang, Liang-min <liang-min.wang@intel.com>;
> > daniels@research.att.com; ktraynor@redhat.com
> > Cc: Wang, Haiyue <haiyue.wang@intel.com>; stable@dpdk.org
> > Subject: [PATCH v2] net/ixgbevf: add an option pflink_fullchk to get
> > link status nowait
> >
> > To get the VF's link status by calling 'rte_eth_link_get_nowait()',
> > the VF not only check PF's physical link status, but also check the mailbox
> running status.
> > And mailbox checking will generate mailbox interrupt in PF, it will be
> > worse if many VFs are running in the system, the PF will have to
> > handle many interrrupts.


interrupts

> >
> > Normally, checking the PF's physical link status is enough for nowait.
> > For different scenarios, adding an 'pflink_fullchk' option to control
> > whether to check the link fully or not.
> 
> Seems the patch change the default behavior which is always "fully check", I
> assume a no fully check does not guarantee the link status is synced correctly,
> right?
> should we implement this devargs in an inverse way to avoid the inconsistent
> with previous version?
> From my view correctness should take high priority than performance.

Checked with author, actually below patch change the default behavior on nowait case
Fixes: 91546fb62e67 ("net/ixgbevf: fix link state")
The patch roll it back and add devarg option for specific requirement, that make sense.

Applied to dpdk-next-net-intel.

Thanks
Qi

      parent reply	other threads:[~2019-06-11  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 15:56 Haiyue Wang
2019-06-07 16:08 ` Scott Daniels
2019-06-10 11:17 ` Zhang, Qi Z
2019-06-11  1:00   ` Wang, Haiyue
2019-06-11  1:29 ` Zhang, Qi Z [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=039ED4275CED7440929022BC67E706115339A0DD@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=daniels@research.att.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=liang-min.wang@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@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
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).