From: Lawrence MacIntyre <macintyrelp@ornl.gov>
To: users@dpdk.org
Subject: [dpdk-users] Jumbo Packet Support
Date: Mon, 14 Dec 2015 13:51:54 -0500 [thread overview]
Message-ID: <566F0FCA.4010706@ornl.gov> (raw)
Hi:
I am attempting to use DPDK v2.1.0 and noticed that there appears to be
nascent support for jumbo packets. For example, in the example
application l2fwd, the comments reference an EAL parameter
--enable-jumbo. However, in the EAL library routines, that parameter
doesn't exist. I looked into the librte_ether/rte_ethdev.c routine and
found that if I modify the l2fwd example as so:
modify Line 119:
.jumbo_frame = 0
to
.jumbo_frame = 1,
.max_rx_pkt_len = 9000,
that the program will compile and run, but any packets larger than 2006
bytes are truncated. What do I need to do in order to make the program
support jumbo packets (9000 bytes in my case)? Or is there a different
but better way to support 9000 byte packets at rates close to 10 Gb/s?
Thanks,
Lawrence
--
Lawrence MacIntyre macintyrelp@ornl.gov Oak Ridge National Laboratory
865.574.7401 Cyber Space and Information Intelligence Research Group
next reply other threads:[~2015-12-14 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:51 Lawrence MacIntyre [this message]
2018-03-27 12:48 mohammad reza piroozi
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=566F0FCA.4010706@ornl.gov \
--to=macintyrelp@ornl.gov \
--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).