From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: husainee <husainee.plumber@nevisnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Random packet drops with ip_pipeline on R730.
Date: Tue, 8 Sep 2015 13:02:52 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478B8A04@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <55EE6A46.6030507@nevisnetworks.com>
Hi Husainee,
Can you please explain what do you mean by random packet drops? What percentage of the input packets get dropped, does it take place on every run, does the number of dropped packets vary on every run, etc?
Are you also able to reproduce this issue with other NICs, e.g. 10GbE NIC?
Can you share your config file?
Can you please double check the low level NIC settings between the two applications, i.e. the settings in structures link_params_default, default_hwq_in_params, default_hwq_out_params from ip_pipeline file config_parse.c vs. their equivalents from l2fwd? The only thing I can think of right now is maybe one of the low level threshold values for the Ethernet link is not tuned for your 1GbE NIC.
Regards,
Cristian
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of husainee
> Sent: Tuesday, September 8, 2015 7:56 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Random packet drops with ip_pipeline on R730.
>
> Hi
>
> I am using a DELL730 with Dual socket. Processor in each socket is
> Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz- 6Cores.
> The CPU layout has socket 0 with 0,2,4,6,8,10 cores and socket 1 with
> 1,3,5,7,9,11 cores.
> The NIC card is i350.
>
> The Cores 2-11 are isolated using isolcpus kernel parameter. We are
> running the ip_peipeline application with only Master, RX and TX threads
> (Flow and Route have been removed from cfg file). The threads are run as
> follows
>
> - Master on CPU core 2
> - RX on CPU core 4
> - TX on CPU core 6
>
> 64 byte packets are sent from ixia at different speeds, but we are
> seeing random packet drops. Same excercise is done on core 3,5,7 and
> results are same.
>
> We tried the l2fwd app and it works fine with no packet drops.
>
> Hugepages per 1024 x 2M per socket.
>
>
> Can anyone suggest what could be the reason for these random packet
> drops.
>
> regards
> husainee
>
>
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2015-09-08 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 4:55 husainee
2015-09-08 13:02 ` Dumitrescu, Cristian [this message]
2015-09-09 9:47 ` husainee
2015-09-09 11:39 ` Dumitrescu, Cristian
2015-09-09 12:15 ` husainee
2015-09-09 16:31 ` Dumitrescu, Cristian
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=3EB4FA525960D640B5BDFFD6A3D89126478B8A04@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=husainee.plumber@nevisnetworks.com \
/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).