From: Apeksha Gupta <apeksha.gupta@nxp.com>
To: akhil.goyal@nxp.com
Cc: thomas@monjalon.net, dev@dpdk.org, hemant.agrawal@nxp.com,
Apeksha Gupta <apeksha.gupta@nxp.com>,
stable@dpdk.org
Subject: [dpdk-dev] [PATCH] config: update MAX_FRAG to support jumbo packets
Date: Wed, 1 Apr 2020 14:05:32 +0530 [thread overview]
Message-ID: <20200401083532.13658-1-apeksha.gupta@nxp.com> (raw)
RTE_LIBRTE_IP_FRAG_MAX_FRAG flag value increased from 4 to 8. By this
pkt size greater than 6000 is supported in ip-fragmentation and
ip-reassembly.
Fixes: 9788b93b9d5 ("config: MAX_FRAG updated to support the jumbo
packets")
Cc: stable@dpdk.org
Signed-off-by: Apeksha Gupta <apeksha.gupta@nxp.com>
---
config/common_base | 2 +-
config/rte_config.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/config/common_base b/config/common_base
index e231384e88..be4a6bafb5 100644
--- a/config/common_base
+++ b/config/common_base
@@ -950,7 +950,7 @@ CONFIG_RTE_LIBRTE_NET=y
#
CONFIG_RTE_LIBRTE_IP_FRAG=y
CONFIG_RTE_LIBRTE_IP_FRAG_DEBUG=n
-CONFIG_RTE_LIBRTE_IP_FRAG_MAX_FRAG=4
+CONFIG_RTE_LIBRTE_IP_FRAG_MAX_FRAG=8
CONFIG_RTE_LIBRTE_IP_FRAG_TBL_STAT=n
#
diff --git a/config/rte_config.h b/config/rte_config.h
index d30786bc08..f5cdc3ddbe 100644
--- a/config/rte_config.h
+++ b/config/rte_config.h
@@ -82,7 +82,7 @@
#define RTE_RAWDEV_MAX_DEVS 64
/* ip_fragmentation defines */
-#define RTE_LIBRTE_IP_FRAG_MAX_FRAG 4
+#define RTE_LIBRTE_IP_FRAG_MAX_FRAG 8
#undef RTE_LIBRTE_IP_FRAG_TBL_STAT
/* rte_power defines */
--
2.17.1
next reply other threads:[~2020-04-01 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 8:35 Apeksha Gupta [this message]
2020-04-06 16:55 ` Ananyev, Konstantin
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=20200401083532.13658-1-apeksha.gupta@nxp.com \
--to=apeksha.gupta@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).