From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Long Li <longli@microsoft.com>,
Sam Andrew <samandrew@microsoft.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3] net/netvsc: add support for mtu_set
Date: Wed, 11 Oct 2023 12:03:26 +0100 [thread overview]
Message-ID: <dff403ce-619c-4cda-82c9-292bf000abb4@amd.com> (raw)
In-Reply-To: <PH7PR21MB3263C64BB0C803A8E3FE0444CECDA@PH7PR21MB3263.namprd21.prod.outlook.com>
On 10/10/2023 8:08 PM, Long Li wrote:
>> Subject: [PATCH v3] net/netvsc: add support for mtu_set
>>
>> Add support for changing the netvsc MTU. The MTU can only be set at nvs
>> initialization, therefore to change the MTU the underlying vmbus
>> channel(s) are torn down and the vmbus device unmapped and remapped. The
>> existing rx and tx queue(s) are reconnected to the new vmbus channel(s).
>>
>> Signed-off-by: Sam Andrew <samandrew@microsoft.com>
>> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Acked-by: Long Li <longli@microsoft.com>
>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2023-10-11 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 23:17 [PATCH] " Sam Andrew
2023-10-06 20:09 ` [PATCH v2] " Sam Andrew
2023-10-06 20:17 ` Stephen Hemminger
2023-10-06 20:22 ` Stephen Hemminger
2023-10-10 15:55 ` Stephen Hemminger
2023-10-10 18:41 ` [PATCH v3] " Sam Andrew
2023-10-10 19:08 ` Long Li
2023-10-11 11:03 ` Ferruh Yigit [this message]
2023-10-09 15:17 ` [PATCH] " Stephen Hemminger
2023-10-09 16:41 ` [EXTERNAL] " Sam Andrew
2023-10-10 15:55 ` Stephen Hemminger
2023-10-31 2:16 ` Rahul Gupta
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=dff403ce-619c-4cda-82c9-292bf000abb4@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=samandrew@microsoft.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).