DPDK patches and discussions
 help / color / mirror / Atom feed
From: Francesco Mancino <francesco.mancino@tutus.se>
To: dev@dpdk.org
Subject: [PATCH v7] net/tap: Allow jumbo frames
Date: Mon, 8 Aug 2022 16:49:44 +0200	[thread overview]
Message-ID: <b5d75b0a-6421-75a5-b7dc-b40597c91eef@tutus.se> (raw)
In-Reply-To: <315474c3-7004-2114-9e24-8344da7aca9e@tutus.se>

eth_dev_validate_mtu, introduced in 990912e676e, validates configured
MTU plus overhead against max_rx_pktlen.
Since TAP is a virtual device, it should support as big MTU as possible.

Signed-off-by: Francesco Mancino <francesco.mancino@tutus.se>
---
 drivers/net/tap/rte_eth_tap.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
index 9e1032fe72..df7f948972 100644
--- a/drivers/net/tap/rte_eth_tap.c
+++ b/drivers/net/tap/rte_eth_tap.c
@@ -1066,7 +1066,7 @@ tap_dev_info(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
 
 	dev_info->if_index = internals->if_index;
 	dev_info->max_mac_addrs = 1;
-	dev_info->max_rx_pktlen = (uint32_t)RTE_ETHER_MAX_VLAN_FRAME_LEN;
+	dev_info->max_rx_pktlen = RTE_ETHER_MAX_JUMBO_FRAME_LEN;
 	dev_info->max_rx_queues = RTE_PMD_TAP_MAX_QUEUES;
 	dev_info->max_tx_queues = RTE_PMD_TAP_MAX_QUEUES;
 	dev_info->min_rx_bufsize = 0;
-- 
2.34.1



  parent reply	other threads:[~2022-08-08 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  9:31 [PATCH] " Francesco Mancino
2022-08-08 14:41 ` Stephen Hemminger
2022-08-08 14:49 ` Francesco Mancino [this message]
2022-08-08 15:03   ` [PATCH v7] " Stephen Hemminger
2022-08-08 15:38     ` Francesco Mancino
2022-08-08 16:42       ` Stephen Hemminger
2022-08-09  7:57         ` Francesco Mancino
2023-01-19 14:50     ` 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=b5d75b0a-6421-75a5-b7dc-b40597c91eef@tutus.se \
    --to=francesco.mancino@tutus.se \
    --cc=dev@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).