From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org, helin.zhang@intel.com, konstantin.ananyev@intel.com
Cc: Guo Fengtian <fengtian.guo@6wind.com>,
stable@dpdk.org, David Marchand <david.marchand@6wind.com>
Subject: Re: [PATCH] net/ixgbevf: reset hardware when stopping port
Date: Mon, 6 Feb 2017 14:58:57 +0100 [thread overview]
Message-ID: <20170206145857.34cc54da@platinum> (raw)
In-Reply-To: <1484153524-19337-1-git-send-email-olivier.matz@6wind.com>
Hi,
On Wed, 11 Jan 2017 17:52:04 +0100, Olivier Matz
<olivier.matz@6wind.com> wrote:
> From: Guo Fengtian <fengtian.guo@6wind.com>
>
> When PF triggers a reset, VF port must acknowledge it by calling
> ixgbe_reset_hw().
>
> Before this patch, the port link status, speed and duplex are invalid
> (all set to 0).
>
> The patch move the call to ixgbe_reset_hw() from ixgbevf_dev_close()
> to ixgbevf_dev_stop(), so that after a port restart on the VM, the
> link status is properly marked down, with correct speed and duplex.
>
> Fixes: f0160874c041 ("ixgbe: various updates")
>
> CC: stable@dpdk.org
> Signed-off-by: Guo Fengtian <fengtian.guo@6wind.com>
> Signed-off-by: David Marchand <david.marchand@6wind.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> ---
>
> Hi,
>
> The use case for this problem was described some time ago, see:
> http://dpdk.org/ml/archives/dev/2015-December/030067.html
>
> It is also part of 2.2 release note:
> http://dpdk.org/browse/dpdk/tree/doc/guides/rel_notes/release_2_2.rst#n471
>
> Regards,
> Olivier
Ping
Thanks,
Olivier
next prev parent reply other threads:[~2017-02-06 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 16:52 [PATCH] net/ixgbevf: reset hardware when stopping port Olivier Matz
2017-02-06 13:58 ` Olivier Matz [this message]
2017-02-24 5:21 ` Lu, Wenzhuo
2017-02-24 8:47 ` [PATCH] net/ixgbevf: reset hardware when stoppingport fengtian Guo
2017-02-24 8:54 ` Lu, Wenzhuo
2017-02-24 10:15 ` [PATCH] net/ixgbevf: reset hardware whenstoppingport fengtian Guo
2017-02-24 10:42 ` Olivier Matz
2017-02-27 14:21 ` Olivier Matz
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=20170206145857.34cc54da@platinum \
--to=olivier.matz@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=fengtian.guo@6wind.com \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@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 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.