From: spyroot <spyroot@gmail.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Jochen Behrens <jochen.behrens@broadcom.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, "Ronak Doshi" <ronak.doshi@broadcom.com>
Subject: Re: [PATCH v3 2/2] net/vmxnet3: support larger MTU with version 6
Date: Sun, 30 Mar 2025 17:46:58 +0400 [thread overview]
Message-ID: <CABsV3rA0zJYXShScu5i-zXM6L-UGhK4PWYDq3a4cNZWjXbM+ZQ@mail.gmail.com> (raw)
In-Reply-To: <a28fa969-d4fc-435c-945c-e510a70bf69e@amd.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hi Folks, how can you bump them VMXNET3 version, and do we have a VMXNET3
unit test for RSS / Max mtu and 32 queue?
On Wed, Nov 6, 2024 at 8:00 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 11/4/2024 9:44 PM, Jochen Behrens wrote:
>
> > On 11/4/24 02:52, Morten Brørup wrote:
> >> Virtual hardware version 6 supports larger max MTU, but the device
> >> information (dev_info) did not reflect this, so it could not be used.
> >>
> >> Fixes: b1584dd0affe ("net/vmxnet3: support version 6")
> >>
> >> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> >
> > Acked-by: Jochen Behrens jochen.behrens@broadcom.com
> >
>
> Applied to dpdk-next-net/main, thanks.
>
[-- Attachment #2: Type: text/html, Size: 1212 bytes --]
next prev parent reply other threads:[~2025-03-30 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 11:01 [PATCH] net/vmxnet3: support per-queue stats for less queues Morten Brørup
2024-10-25 9:27 ` [PATCH v2] net/vmxnet3: support per-queue stats for fewer queues Morten Brørup
2024-10-27 8:47 ` Morten Brørup
2024-11-01 0:28 ` Ferruh Yigit
2024-11-04 10:52 ` [PATCH v3 1/2] net/vmxnet3: fix potential out of bounds access Morten Brørup
2024-11-04 10:52 ` [PATCH v3 2/2] net/vmxnet3: support larger MTU with version 6 Morten Brørup
2024-11-04 21:44 ` Jochen Behrens
2024-11-06 2:04 ` Ferruh Yigit
2025-03-30 13:46 ` spyroot [this message]
2024-11-06 2:04 ` [PATCH v3 1/2] net/vmxnet3: fix potential out of bounds access 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=CABsV3rA0zJYXShScu5i-zXM6L-UGhK4PWYDq3a4cNZWjXbM+ZQ@mail.gmail.com \
--to=spyroot@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jochen.behrens@broadcom.com \
--cc=mb@smartsharesystems.com \
--cc=ronak.doshi@broadcom.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).