From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>, dev@dpdk.org
Cc: Dept-EngDPDKDev@cavium.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] net/qede: fix to update VF MTU
Date: Thu, 31 May 2018 17:35:37 +0100 [thread overview]
Message-ID: <a534af1c-edba-36b2-d417-2abe474a0e90@intel.com> (raw)
In-Reply-To: <1527030964-17525-1-git-send-email-rasesh.mody@cavium.com>
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>
Series applied to dpdk-next-net/master, thanks.
(for v18.08)
prev parent reply other threads:[~2018-05-31 16:35 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
2018-05-31 16:35 ` 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=a534af1c-edba-36b2-d417-2abe474a0e90@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--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).