From: Bob Cochran <yocto@mindchasers.com>
To: Clemens Eisserer <linuxhippy@gmail.com>, meta-freescale@yoctoproject.org
Subject: Re: UDP jumbo packet loss on T2080RDB and out-of-order receive
Date: Tue, 10 Nov 2015 21:43:40 -0500 [thread overview]
Message-ID: <5642AB5C.4020606@mindchasers.com> (raw)
In-Reply-To: <CAFvQSYSuZauZxa7xOFOTQ=aaoHALbER08P+F+3wz95LYxeF8XA@mail.gmail.com>
On 11/10/2015 11:17 AM, Clemens Eisserer wrote:
> Hi,
>
> I am trying to receive a stream of 9k jumbo frames on one of our
> T2080RDBs (simply using recvfrom), however even a very low rate
> (12MB/s on average) frequently UDP packages are lost. Furthermore the
> packets are received out-of-order e.g. :0, 8, 1, 2, 10, 3, 11, 4, 5,
> 6, .....
> While receiving the stream, I see an equal number of interrupts on
> QMAN-Portal0 through QMAN-Portal-7.
> PF_PACKET / PACKET_RX_RING for packet capturing also doesn't seem to
> work - is this unsupported by DPAA?
>
> So to summerize - any idea what could cause the following issues:
> * UDP jumbo packet loss
> * UDP jumbo packets are received out-of-order
>
> Thank you in advance, Clemens
>
Tracing is implemented for the DPAA. If you haven't done it already, you
might want to enable it to get a better idea how each packet is being
handled. Once you get it working, it's pretty easy to add some
additional fields and rebuild the kernel.
Events like dpa_rx_fd and dpa_tx_fd are supported and can be found in
the dpa source directory under drivers.
There is also a Freescale DPAA Packet Tool that offers a free trial.
It pretty much provides the same information as trace but with a GUI;
however, it might require a JTAG TAP ( that's how I use it ).
Bob
prev parent reply other threads:[~2015-11-11 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 16:17 UDP jumbo packet loss on T2080RDB and out-of-order receive Clemens Eisserer
2015-11-10 21:29 ` Fabio Estevam
2015-11-11 2:10 ` Luo Zhenhua
2015-11-11 15:26 ` Clemens Eisserer
2015-11-11 2:43 ` Bob Cochran [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=5642AB5C.4020606@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=linuxhippy@gmail.com \
--cc=meta-freescale@yoctoproject.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 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.