From: "Wiles, Keith" <keith.wiles@intel.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK - Network
Date: Thu, 15 Dec 2016 14:49:06 +0000 [thread overview]
Message-ID: <665D0ED3-AC22-47F5-B53F-9BCDCF3EF5EA@intel.com> (raw)
In-Reply-To: <38A3B6CE-2607-45F8-B786-5A841C618B89@cloudsimple.com>
> On Dec 15, 2016, at 8:17 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>
> Hi All,
>
> The MTU by default is 1500. But for the RX_BUFFER the packet size should atleast be 2048. So does this mean that for DPDK to work there should be MTU of atleast 2048?
DPDK uses 2048 byte buffers for aligning memory as 1500 is and odd size for memory buffers. You should still use the standard MTU values for non-jumbo frames.
>
> Thanking You,
> Param.
Regards,
Keith
prev parent reply other threads:[~2016-12-15 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 14:17 Kumaraparameshwaran Rathnavel
2016-12-15 14:49 ` Wiles, Keith [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=665D0ED3-AC22-47F5-B53F-9BCDCF3EF5EA@intel.com \
--to=keith.wiles@intel.com \
--cc=krath@cloudsimple.com \
--cc=users@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).