From: Thomas Monjalon <thomas@monjalon.net>
To: Noa Ezra <noae@mellanox.com>
Cc: dev@dpdk.org, "Ananyev,
Konstantin" <konstantin.ananyev@intel.com>,
Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples/ip_fragmentation: support big packets
Date: Tue, 15 Jan 2019 01:21:12 +0100 [thread overview]
Message-ID: <14746990.gd7JFLnMxP@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258010D903A68@irsmsx105.ger.corp.intel.com>
14/01/2019 13:55, Ananyev, Konstantin:
> >
> > 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>
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-15 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 11:37 Noa Ezra
2019-01-14 12:55 ` Ananyev, Konstantin
2019-01-15 0:21 ` Thomas Monjalon [this message]
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=14746990.gd7JFLnMxP@xps \
--to=thomas@monjalon.net \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=noae@mellanox.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).