[dpdk-dev] Random packet drops with ip_pipeline on R730.

[husainee]

Hi Cristian
PFA the config file.

I am sending packets from port0 and receiving on port1.

By random packet drops I mean, on every run the number of packets
dropped is not same. Here are some results as below.

Frame sent rate 1488095.2 fps, 64Byte packets (100% of 1000Mbps)
Run1- 0.0098% (20-22 Million Packets)
Run2- 0.021% (20-22 Million Packets)
Run3- 0.0091% (20-22 Million Packets)

Frame rate 744047.62 fps, 64 Byte packets, (50% of 1000Mbps)
Run1- 0.0047% (20-22 Million Packets)
Run2- 0.0040% (20-22 Million Packets)
Run3- 0.0040% (20-22 Million Packets)


Frame rate 148809.52 fps, 64 Byte packets,(10% of 1000Mbps)
Run1- 0 (20-22 Million Packets)
Run2- 0 (20-22 Million Packets)
Run3- 0 (20-22 Million Packets)



Following are the hw nic setting differences btw ip_pipeline and l2fwd app.

parameter
	ip_pipeline
	l2fwd
jumbo frame
	1
	0
hw_ip_checksum
	1
	0
rx_conf. wthresh
	4
	0
rx_conf.rx_free_thresh
	64
	32
tx_conf.pthresh
	36
	32
burst size
	64
	32


We tried to make the ip_pipeline settings same as l2fwd but no change in
results.

I have not tried with 10GbE . I do not have 10GbE test equipment.



regards
husainee




On 09/08/2015 06:32 PM, Dumitrescu, Cristian wrote:
> 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 at dpdk.org] On Behalf Of husainee
>> Sent: Tuesday, September 8, 2015 7:56 AM
>> To: dev at 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 part --------------
;   BSD LICENSE
;
;   Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
;   All rights reserved.
;
;   Redistribution and use in source and binary forms, with or without
;   modification, are permitted provided that the following conditions
;   are met:
;
;     * Redistributions of source code must retain the above copyright
;       notice, this list of conditions and the following disclaimer.
;     * Redistributions in binary form must reproduce the above copyright
;       notice, this list of conditions and the following disclaimer in
;       the documentation and/or other materials provided with the
;       distribution.
;     * Neither the name of Intel Corporation nor the names of its
;       contributors may be used to endorse or promote products derived
;       from this software without specific prior written permission.
;
;   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
;   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
;   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
;   A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
;   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
;   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
;   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
;   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
;   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
;   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
;   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

; Core configuration
[core 0]
type = MASTER
queues in  = 5 -1 -1 -1 -1 -1 -1 -1
queues out = 4 -1 -1  -1 -1 -1 -1 -1

[core 1]
type = RX
queues in  = -1 -1 -1 -1 -1 -1 -1 4
queues out =  0  1  2  3 -1 -1 -1 5

;[core 2]
;type = FC
;queues in  =  0  1  2  3 -1 -1 -1 9
;queues out =  4  5  6  7 -1 -1 -1 11


[core 2]
type = TX
queues in  =  1 0 2 3 -1 -1 -1 -1
queues out = -1 -1 -1 -1 -1 -1 -1 -1