DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Guo, Jia" <jia.guo@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Helin" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add known PHY link up issue for i40e
Date: Thu, 8 Nov 2018 07:05:41 +0000	[thread overview]
Message-ID: <01BA8470C017D6468C8290E4B9C5E1E83F9F59D5@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E70611532CA9B8@SHSMSX103.ccr.corp.intel.com>

Hi, qi

Mostly accept, please check v2 version for that, thanks.

Best regards,
Jeff Guo

-----Original Message-----
From: Zhang, Qi Z 
Sent: Saturday, October 20, 2018 2:05 AM
To: Guo, Jia <jia.guo@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Mcnamara, John <john.mcnamara@intel.com>; Kovacevic, Marko <marko.kovacevic@intel.com>
Cc: Wu, Jingjing <jingjing.wu@intel.com>; dev@dpdk.org; Zhang, Helin <helin.zhang@intel.com>
Subject: RE: [PATCH] doc: add known PHY link up issue for i40e

Hi Jeff:

	
> -----Original Message-----
> From: Guo, Jia
> Sent: Thursday, October 11, 2018 4:09 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Xing, Beilei 
> <beilei.xing@intel.com>; Mcnamara, John <john.mcnamara@intel.com>; 
> Kovacevic, Marko <marko.kovacevic@intel.com>
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; dev@dpdk.org; Guo, Jia 
> <jia.guo@intel.com>; Zhang, Helin <helin.zhang@intel.com>
> Subject: [PATCH] doc: add known PHY link up issue for i40e
> 
> When application stop i40e nics and quit itself, if i40e nics be 
> rebinded from pmd to kernel driver, sometimes PHY can not be link up again any more.

Better use capital letter for NIC , PMD.

s/stop/stops

s/rebinded/rebound

s/can not/cannot


> 
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
> ---
>  doc/guides/rel_notes/known_issues.rst | 27
> +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/known_issues.rst
> b/doc/guides/rel_notes/known_issues.rst
> index 95e4ce6..3378bb7 100644
> --- a/doc/guides/rel_notes/known_issues.rst
> +++ b/doc/guides/rel_notes/known_issues.rst
> @@ -759,3 +759,30 @@ Netvsc driver and application restart
> 
>  **Driver/Module**:
>     ``uio_hv_generic`` module.
> +
> +
> +PHY link up failed when rebind i40e nics to kernel driver
> +---------------------------------------------------------
> +
> +**Description**:
> +   When application stop i40e nics and quit itself, if i40e nics be rebinded
> +   from pmd to kernel driver, sometimes PHY can not be link up again 
> +any
> more.

Besides the spell, grammar fix as previous, I think the content here should be swapped with the content in **Implication**


> +
> +**Implication**:
> +   when DPDK application quit and invoke the function 
> +``i40e_dev_stop``,
> I40e
> +   pmd will set PHY to be link down. After these unexpected configure
> which not
> +   come from kernel driver,

Not very clear about this statement.
Are you going to say:

Before DPDK application quit, it will invoke the function ````i40e_dev_stop`` which will set PHY to link down.
This is the situation that some kernel driver may not able to handle link status correctly after it retakes control of the device.

I think some reword is necessary here

> + it will encounter link configure failure by using
> +   kernel driver config tools ``ifconfig``. It is a known PHY link 
> + configure

No need "kernel driver config tools ``ifconfig``" , just ``ifconfig`` should be enough

> +   synchronous issue in i40e kernel driver. The fix has been 
> + addressed in
> 2.7.4
> +   rc version. So if the i40e kernel driver is < 2.7.4 and before the fix be
> +   backported into the privous versions, use these kernel drivers 
> + will
> perhaps
> +   have this issue.


> +
> +**Resolution/Workaround**:
> +   If it does not help by re-insmod kernel driver, please reboot system.

remove and re-insert?

If it does not help by remove and insert i40e kernel driver, please reboot the system.

> +
> +**Affected E0nvironment/Platform**:

Environment 

> +   All.
> +
> +**Driver/Module**:
> +   Poll Mode Driver (PMD).
> --
> 2.7.4

  reply	other threads:[~2018-11-08  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 11:08 Jeff Guo
2018-10-19 18:05 ` Zhang, Qi Z
2018-11-08  7:05   ` Guo, Jia [this message]
2018-11-08  7:17 ` [dpdk-dev] [PATCH V2] " Jeff Guo
2018-11-08 17:48   ` Zhang, Qi Z
2018-11-09  2:21     ` Jeff Guo
2018-11-09 16:31       ` Zhang, Qi Z
2018-11-16  2:38 ` [dpdk-dev] [PATCH V3] " Jeff Guo
2018-11-16  9:41   ` Kovacevic, Marko
2018-11-16 19:32     ` Zhang, Qi Z
  -- strict thread matches above, loose matches on Subject: below --
2018-10-11 11:04 [dpdk-dev] [PATCH] " Jeff Guo

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=01BA8470C017D6468C8290E4B9C5E1E83F9F59D5@shsmsx102.ccr.corp.intel.com \
    --to=jia.guo@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=qi.z.zhang@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).