DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ariel Rodriguez <arodriguez@callistech.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev]  Problem after hours of running rte_eth_rx_burst
Date: Tue, 3 Nov 2015 19:25:53 -0300	[thread overview]
Message-ID: <CADoa0bZWCNXYY73n4AbT1amhGbEb2Z6ewzm6DD_TWzsZv0_Z1A@mail.gmail.com> (raw)

After several hours (6 hour average) of running a dpdk application
, rte_eth_rx_burst suddenly fills only one mbuf with no data, thats is an
mbuf with mbuf->pool == NULL && m->buf_physaddr == 0 && m->buf_addr == NULL.

Obviosly that breaks our application.  (rte_mbuf_sanity_check abort the
program)

How can we track the source of this kind of mis- behavoir?

We are using dpdk 1.6.0r2 and we also use the qos framework api.

The nic is 82599ES 10-Gigabit SFI/SFP+ with tapped traffic.

The use case is simply, our client is using a traffic tap to divert a copy
of around 10gbps of traffic to our appliance. We use a rxtx code similar to
the load_balancer example. We read in a pair of rx queue and the use a hash
function over the source ip field to deliver the packet in a worker core.

Then , when the worker core finishes to process that packet and it is
delivery to the tx core.

The tx core enqueue the packet to the qos framework, and just a few lines
code later dequeue several packet from the qos scheduler. Because we are
using a tap to divert a copy of the traffic , we disable the tx code to the
phisycal nic, so when we dequeue packets from the qos scheduler wi just
drop all of that packets.

Of course there is a reason why we use the qos scheduler code without
physically transmiting a packet, and is because we just want a few stats
about the qos framework behaviour.


Any ideas?

                 reply	other threads:[~2015-11-03 22:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADoa0bZWCNXYY73n4AbT1amhGbEb2Z6ewzm6DD_TWzsZv0_Z1A@mail.gmail.com \
    --to=arodriguez@callistech.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).