From: Newman Poborsky <newman555p@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] issues with packets bigger than 1500 bytes
Date: Mon, 30 Mar 2015 12:52:22 +0200 [thread overview]
Message-ID: <20150330094416.GA22583@fedex> (raw)
Hi,
I'm having some problems with dpdk on links that have packets bigger
than 1500bytes. Some packets that are receieved are around 4K, and
some are 9k jumbo frames.
When using testpmd app, I can see a lot of RX-errors (both RX-missed and RX-badlen). When I set max packet length to 9000, RX-badlen counter stops increasing, but RX-missed still keeps growing.
What is the proper way to deal with jumbo frames?
I tried setting MTU to 9k, but this fails. From what I can see, you have to pass additional parameter to mp_init callback in rte_mempool_create(). Is this right?
I'm not sure should I just set max packet length (like in testpmd example app), or should I (also) set MTU? Is this actually related to the original problem of having a lot of RX-missed packets?
If I missed some documentation related to jumbo frames and MTU, I apologize, please point me to it.
Any help is appreciated.
Thank you,
Newman P.
next reply other threads:[~2015-03-30 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:52 Newman Poborsky [this message]
2015-03-31 13:33 ` Newman Poborsky
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=20150330094416.GA22583@fedex \
--to=newman555p@gmail.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).