From: Scott Daniels <daniels@research.att.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com, wenzhuo.lu@intel.com,
liang-min.wang@intel.com, ktraynor@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbevf: add an option pflink_fullchk to get link status nowait
Date: Fri, 7 Jun 2019 12:08:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LSU.2.20.12.1906071206180.12860@localhost> (raw)
In-Reply-To: <1559922981-101848-1-git-send-email-haiyue.wang@intel.com>
Acked-by: Scott Daniels daniels@research.att.com
On Fri, 7 Jun 2019, Haiyue Wang wrote:
> 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.
>
> 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.
>
> Fixes: 91546fb62e67 ("net/ixgbevf: fix link state")
> Cc: stable@dpdk.org
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
next prev parent reply other threads:[~2019-06-07 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 15:56 [dpdk-dev] [PATCH v2] net/ixgbevf: add an option pflink_fullchk to get link status nowait Haiyue Wang
2019-06-07 16:08 ` Scott Daniels [this message]
2019-06-10 11:17 ` Zhang, Qi Z
2019-06-11 1:00 ` Wang, Haiyue
2019-06-11 1:29 ` 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=alpine.LSU.2.20.12.1906071206180.12860@localhost \
--to=daniels@research.att.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=ktraynor@redhat.com \
--cc=liang-min.wang@intel.com \
--cc=qi.z.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.