From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/qede: fix to update VF MTU
Date: Wed, 23 May 2018 17:16:05 +0000 [thread overview]
Message-ID: <MWHPR0701MB36750CFD711738CD2FD6D3F49F6B0@MWHPR0701MB3675.namprd07.prod.outlook.com> (raw)
In-Reply-To: <99a89532-6151-defe-99f8-212a525dfae1@intel.com>
Hi Ferruh,
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Wednesday, May 23, 2018 8:48 AM
>
> On 5/23/2018 12:16 AM, Rasesh Mody wrote:
> > This patch fixes VF MTU update to work without having to restart the
> > vport and there by not requiring port re-configuration. It adds a VF
> > MTU Update TLV to achieve the same. Firmware can handle VF MTU
> update
> > by just pausing the vport.
> >
> > Fixes: dd28bc8c6ef4 ("net/qede: fix VF port creation sequence")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
>
> Hi Rasesh,
>
> This patchset was late for rc5, it will be considered for next release.
The patchset is fixing important issues with QEDE PMD in 18.05.
This patch fixes loss of port configuration by the application when changing/updating the MTU. The following patch in the set fixes application crash when wrong devarg is supplied or when VF devarg is supplied in PF environment.
Could you please include these fixes in 18.05 release?
Thanks!
-Rasesh
>
> Thanks,
> ferruh
next prev parent reply other threads:[~2018-05-23 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 23:16 Rasesh Mody
2018-05-22 23:16 ` [dpdk-dev] [PATCH 2/2] net/qede: fix for devargs Rasesh Mody
2018-05-23 15:47 ` [dpdk-dev] [PATCH 1/2] net/qede: fix to update VF MTU Ferruh Yigit
2018-05-23 17:16 ` Mody, Rasesh [this message]
2018-05-31 16:35 ` Ferruh Yigit
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=MWHPR0701MB36750CFD711738CD2FD6D3F49F6B0@MWHPR0701MB3675.namprd07.prod.outlook.com \
--to=rasesh.mody@cavium.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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 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).