From: Jochen Behrens <jochen.behrens@broadcom.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, "Ferruh Yigit" <ferruh.yigit@amd.com>,
"Ronak Doshi" <ronak.doshi@broadcom.com>
Subject: Re: [PATCH v3 2/2] net/vmxnet3: support larger MTU with version 6
Date: Mon, 4 Nov 2024 13:44:13 -0800 [thread overview]
Message-ID: <f942d7c7-7aa6-4ba0-a624-384d11b118ac@broadcom.com> (raw)
In-Reply-To: <20241104105220.1421305-2-mb@smartsharesystems.com>
Hi Morten,
thanks for fixing the MTU setting!
Acked-by: Jochen Behrens jochen.behrens@broadcom.com
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>
> ---
> v3:
> * Moved support for larger MTU with virtual hardware version 6 to separate
> patch. (Ferruh Yigit)
> ---
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> index 8a9bb452c6..1752c58069 100644
> --- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
> +++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> @@ -1574,7 +1574,7 @@ vmxnet3_dev_info_get(struct rte_eth_dev *dev,
> dev_info->min_rx_bufsize = 1518 + RTE_PKTMBUF_HEADROOM;
> dev_info->max_rx_pktlen = 16384; /* includes CRC, cf MAXFRS register */
> dev_info->min_mtu = VMXNET3_MIN_MTU;
> - dev_info->max_mtu = VMXNET3_MAX_MTU;
> + dev_info->max_mtu = VMXNET3_VERSION_GE_6(hw) ? VMXNET3_V6_MAX_MTU : VMXNET3_MAX_MTU;
> dev_info->speed_capa = RTE_ETH_LINK_SPEED_10G;
> dev_info->max_mac_addrs = VMXNET3_MAX_MAC_ADDRS;
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
next prev parent reply other threads:[~2024-11-04 21:44 UTC|newest]
Thread overview: 9+ 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 [this message]
2024-11-06 2:04 ` Ferruh Yigit
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=f942d7c7-7aa6-4ba0-a624-384d11b118ac@broadcom.com \
--to=jochen.behrens@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).