All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, Noa Ezra <noae@mellanox.com>
Subject: Re: [PATCH] examples/ip_fragmentation: support bigger packets
Date: Wed, 19 Dec 2018 22:30:56 +0100	[thread overview]
Message-ID: <1896936.vBC4Qs7ps3@xps> (raw)
In-Reply-To: <1544703399-32621-1-git-send-email-noae@mellanox.com>

13/12/2018 13:17, Noa Ezra:
> Adding MTU and mbuf size configuration to the application's command
> line, in order to be able to receive all packet sizes by the NIC and
> DPDK application.
> The maximum transmission unit (MTU) is the largest size packet in
> bytes that can be sent on the network, therefore before adding MTU
> parameter, the NIC could not receive packets larger than 1500 bytes,
> which is the default MTU size.
> The mbuf is the memory buffer that contains the packet. Before adding
> mbuf parameter, the DPDK application could not receive packets larger
> than 2KB, which is the default mbuf size.
> 
> Signed-off-by: Noa Ezra <noae@mellanox.com>
> ---
>  doc/guides/sample_app_ug/ip_frag.rst | 18 ++++++++-
>  examples/ip_fragmentation/main.c     | 77 +++++++++++++++++++++++++++++++++---
>  2 files changed, 88 insertions(+), 7 deletions(-)

Konstantin, any comment please?

  reply	other threads:[~2018-12-19 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 12:17 [PATCH] examples/ip_fragmentation: support bigger packets Noa Ezra
2018-12-19 21:30 ` Thomas Monjalon [this message]
2018-12-20  0:18 ` Ananyev, Konstantin
2018-12-20  9:45   ` Noa Ezra
2018-12-20 12:11     ` 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=1896936.vBC4Qs7ps3@xps \
    --to=thomas@monjalon.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.