DPDK patches and discussions
 help / color / mirror / Atom feed
From: Noa Ezra <noae@mellanox.com>
To: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: Asaf Penso <asafp@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Noa Ezra <noae@mellanox.com>
Subject: [dpdk-dev] [PATCH v2] examples/ip_fragmentation: support big packets
Date: Sun, 13 Jan 2019 11:37:06 +0000	[thread overview]
Message-ID: <1547379358-17310-1-git-send-email-noae@mellanox.com> (raw)

In some vendors the RX and TX configuration must be the same, therefore
the MTU size need to be equal to max_rx_pkt_len.
The MTU is the largest size packet in bytes that can be sent on the
network, therefore before changing this parameter, the NIC could not
receive packets larger than 1500 bytes, which is the default MTU size.
In addition, scatter-gather need to be enabled in order to receive
frames bigger than mbuf size.

Signed-off-by: Noa Ezra <noae@mellanox.com>
---
v2: move set_mtu() to be done after dev_configure().

 examples/ip_fragmentation/main.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/examples/ip_fragmentation/main.c b/examples/ip_fragmentation/main.c
index 17a877d..8d789b4 100644
--- a/examples/ip_fragmentation/main.c
+++ b/examples/ip_fragmentation/main.c
@@ -141,6 +141,7 @@ struct lcore_queue_conf {
 		.max_rx_pkt_len = JUMBO_FRAME_MAX_SIZE,
 		.split_hdr_size = 0,
 		.offloads = (DEV_RX_OFFLOAD_CHECKSUM |
+			     DEV_RX_OFFLOAD_SCATTER |
 			     DEV_RX_OFFLOAD_JUMBO_FRAME),
 	},
 	.txmode = {
@@ -935,6 +936,16 @@ struct rte_lpm6_config lpm6_config = {
 				ret, portid);
 		}
 
+		/* set the mtu to the maximum received packet size */
+		ret = rte_eth_dev_set_mtu(portid,
+			local_port_conf.rxmode.max_rx_pkt_len);
+		if (ret < 0) {
+			printf("\n");
+			rte_exit(EXIT_FAILURE, "Set MTU failed: "
+				"err=%d, port=%d\n",
+			ret, portid);
+		}
+
 		ret = rte_eth_dev_adjust_nb_rx_tx_desc(portid, &nb_rxd,
 					    &nb_txd);
 		if (ret < 0) {
-- 
1.8.3.1

             reply	other threads:[~2019-01-13 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 11:37 Noa Ezra [this message]
2019-01-14 12:55 ` Ananyev, Konstantin
2019-01-15  0:21   ` Thomas Monjalon

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=1547379358-17310-1-git-send-email-noae@mellanox.com \
    --to=noae@mellanox.com \
    --cc=asafp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.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).