DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] port: removed IPV4_MTU_DEFAULT define
Date: Mon, 30 Mar 2015 12:15:15 +0200	[thread overview]
Message-ID: <1427710517-29001-2-git-send-email-maciejx.t.gajdzica@intel.com> (raw)
In-Reply-To: <1427710517-29001-1-git-send-email-maciejx.t.gajdzica@intel.com>

p->mtu field should be used instead.
---
 lib/librte_port/rte_port_frag.c |    6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/lib/librte_port/rte_port_frag.c b/lib/librte_port/rte_port_frag.c
index ff0ab9b..dce33d5 100644
--- a/lib/librte_port/rte_port_frag.c
+++ b/lib/librte_port/rte_port_frag.c
@@ -38,10 +38,6 @@
 
 #include "rte_port_frag.h"
 
-/* Default byte size for the IPv4 Maximum Transfer Unit (MTU).
- * This value includes the size of IPv4 header. */
-#define	IPV4_MTU_DEFAULT ETHER_MTU
-
 /* Max number of fragments per packet allowed */
 #define	IPV4_MAX_FRAGS_PER_PACKET 0x80
 
@@ -160,7 +156,7 @@ rte_port_ring_reader_ipv4_frag_rx(void *port,
 		p->n_pkts--;
 
 		/* If not jumbo, pass current packet to output */
-		if (pkt->pkt_len <= IPV4_MTU_DEFAULT) {
+		if (pkt->pkt_len <= p->mtu) {
 			pkts[n_pkts_out++] = pkt;
 
 			n_pkts_to_provide = n_pkts - n_pkts_out;
-- 
1.7.9.5

  reply	other threads:[~2015-03-30 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 10:15 [dpdk-dev] [PATCH 0/3] port: added frag_ipv6 and ras_ipv6 ports Maciej Gajdzica
2015-03-30 10:15 ` Maciej Gajdzica [this message]
2015-03-30 10:15 ` [dpdk-dev] [PATCH 2/3] port: added ipv6 fragmentation port Maciej Gajdzica
2015-03-30 10:15 ` [dpdk-dev] [PATCH 3/3] port: added ipv6 reassembly port Maciej Gajdzica
2015-03-30 11:56 ` [dpdk-dev] [PATCH 0/3] port: added frag_ipv6 and ras_ipv6 ports Dumitrescu, Cristian
2015-04-28 15:43   ` 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=1427710517-29001-2-git-send-email-maciejx.t.gajdzica@intel.com \
    --to=maciejx.t.gajdzica@intel.com \
    --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).