From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>, dev@dpdk.org
Cc: Harish Patil <harish.patil@cavium.com>,
Dept-EngDPDKDev@cavium.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] net/qede: fix VF vport creation sequence
Date: Mon, 5 Feb 2018 16:34:27 +0000 [thread overview]
Message-ID: <dec7f613-3b8d-6cb7-abcd-0519cf07f256@intel.com> (raw)
In-Reply-To: <1517637799-15390-1-git-send-email-rasesh.mody@cavium.com>
On 2/3/2018 6:03 AM, Rasesh Mody wrote:
> From: Harish Patil <harish.patil@cavium.com>
>
> Few adjustments are required to effectively handle VF vport create/delete
> sequence. The problem is exposed by recent ethdev TX offload changes
> which requires port to be in down state before applying TX offloads.
>
> - Move vport creation from dev_init() to dev_configure()
> - Force to stop vport if it was already started due to previous run
> (restart case)
> - Move link state enable/disable to dev_init() and dev_close()
> respectively.
> - For MTU change, recreate vport with new MTU value and restore old
> config. This is necessary since VF MTU value can be changed only upon
> vport creation.
>
> Fixes: ec94dbc57362 ("qede: add base driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Harish Patil <harish.patil@cavium.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-02-05 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 6:03 Rasesh Mody
2018-02-03 6:03 ` [dpdk-dev] [PATCH 2/3] net/qede: fix few log messages Rasesh Mody
2018-02-03 6:03 ` [dpdk-dev] [PATCH 3/3] doc: qede: align dynamic log names with standard Rasesh Mody
2018-02-05 16:34 ` Ferruh Yigit [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=dec7f613-3b8d-6cb7-abcd-0519cf07f256@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=harish.patil@cavium.com \
--cc=rasesh.mody@cavium.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).