From: Bruce Richardson <bruce.richardson@intel.com>
To: Ariel Rodriguez <arodriguez@callistech.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] URGENT please help. Issue on ixgbe_tx_free_bufs version 2.0.0
Date: Tue, 17 Nov 2015 10:33:17 +0000 [thread overview]
Message-ID: <20151117103316.GA22264@bricha3-MOBL3> (raw)
In-Reply-To: <CADoa0bY4grd74Gn6fxN+T_U9tr5yZax-WoGivtGrLa-hJEuVNQ@mail.gmail.com>
On Sun, Nov 15, 2015 at 07:58:27PM -0300, Ariel Rodriguez wrote:
> Hi Bruce, im going to list the results after the test´s.
>
> I will start with the second hint you proposed:
>
> 2) I upgrade our custom dpdk application with the latest dpdk code (2.1.0)
> and the issue still there.
>
> 1) I test the load balancer app with the latest dpdk code (2.1.0) with the nic
> 82599ES 10-Gigabit SFI/SFP+ with tapped traffic and the results are:
>
> a) Work fine after 6 hours of running. (For timing issues i cant wait
> longer but the issue always happend before 5 hours of running so i supposed
> we are fine in this test).
>
> b) I made a change to load balancer code to behave as our dpdk
> application in the workers code. This change is just for giving the
> workers code enough load (load in terms of core frecuency) that made the rx
> core drop several packet because ring between workers and rx core is full.
> (Our application drop several packets because the workers code are not fast
> enough).
>
> In the last test, the segmentation fault arise , just in the same
> line that i previously report.
>
What is the workload you are putting into the worker core? Can you provide a
diff for the load balancer app that reproduces this issue, since from your
description the problem may be in the extra code added in.
/Bruce
prev parent reply other threads:[~2015-11-17 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 4:35 Ariel Rodriguez
2015-11-10 10:54 ` Bruce Richardson
2015-11-10 11:50 ` Ariel Rodriguez
2015-11-15 22:58 ` Ariel Rodriguez
2015-11-17 10:33 ` Bruce Richardson [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=20151117103316.GA22264@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=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).