RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1571496 - [Mellanox OVS offload] Always has packets loss
Summary: [Mellanox OVS offload] Always has packets loss
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Marcelo Ricardo Leitner
QA Contact: qding
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-25 01:53 UTC by qding
Modified: 2018-04-28 07:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-28 07:58:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description qding 2018-04-25 01:53:21 UTC
Description of problem:

Always has packets loss when running throughput test for OVS offload

[qding@dhcp-12-246 Documents]$ grep -e 'running trial' -e 'percent loss' tc_offload.log
running trial 001, rate 24.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 8.094145%, lost packets: 38551931)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 41.897612%, lost packets: 8315)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 7.152866%, lost packets: 34070304)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 40.976421%, lost packets: 8133)
running trial 002, rate 24.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.164619%, lost packets: 784033)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 38.130511%, lost packets: 7567)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.154735%, lost packets: 736998)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 37.910012%, lost packets: 7524)
running trial 003, rate 24.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.175050%, lost packets: 833826)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 38.685947%, lost packets: 7678)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.175699%, lost packets: 836941)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 38.865377%, lost packets: 7714)
running trial 004, rate 24.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.149610%, lost packets: 712641)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 37.442692%, lost packets: 7432)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.144065%, lost packets: 686245)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 37.783375%, lost packets: 7500)
running trial 005, rate 12.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.001857%, lost packets: 6686)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 22.880000%, lost packets: 6864)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000403%, lost packets: 1449)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 21.013333%, lost packets: 6304)
running trial 006, rate 6.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000686%, lost packets: 1234)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 007, rate 3.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000506%, lost packets: 455)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 008, rate 1.500000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.001020%, lost packets: 459)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 009, rate 1.200000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000083%, lost packets: 30)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
[qding@dhcp-12-246 Documents]$ 

[root@dell-per730-04 ~]# ethtool -i p6p1
driver: mlx5_core
version: 5.0-0
firmware-version: 14.22.1002 (MT_2420110004)
expansion-rom-version: 
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
[root@dell-per730-04 ~]# lspci -m -s 0000:04:00.0
04:00.0 "Ethernet controller" "Mellanox Technologies" "MT27710 Family [ConnectX-4 Lx]" "Mellanox Technologies" "ConnectX-4 Lx Stand-up dual-port 10GbE MCX4121A-XCAT"
[root@dell-per730-04 ~]# 

Version-Release number of selected component (if applicable):
kernel-3.10.0-862.el7.x86_64
beaker job: https://beaker.engineering.redhat.com/jobs/2443129

How reproducible: always


Steps to Reproduce:
1. create two SR-IOV VFs on two PFs separately
2. enable offload
3. add representor to OVS bridge
4. attach two VFs (one for each PF) to a guest
8e749d7f-650e-4c72-8023-7b557c554a22
    Bridge "ovsbr1"
        Port "eth2"
            Interface "eth2"
        Port "p6p2"
            Interface "p6p2"
        Port "ovsbr1"
            Interface "ovsbr1"
                type: internal
    Bridge "ovsbr0"
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
        Port "p6p1"
            Interface "p6p1"
        Port "eth0"
            Interface "eth0"
    ovs_version: "2.9.0"

5. run testpmd in guest
testpmd -l 0-8 -n 9 --socket-mem 1024,0 -w 0000:00:06.0,txq_inline=256 -w 0000:00:07.0,txq_inline=256 -- -i --auto-start --nb-cores=8 --rxq=4 --txq=4 


Actual results:
always has packets loss

Expected results:
no packets loss when rate is reasonable

Additional info:
RPM_OVS=http://download-node-02.eng.bos.redhat.com/brewroot/packages/openvswitch/2.9.0/19.el7fdp/x86_64/openvswitch-2.9.0-19.el7fdp.x86_64.rpm
RPM_DPDK_IN_GUEST=http://download-node-02.eng.bos.redhat.com/brewroot/packages/dpdk/17.11/6.el7fdb/x86_64/dpdk-17.11-6.el7fdb.x86_64.rpm
RPM_DPDK_TOOLS_IN_GUEST=http://download-node-02.eng.bos.redhat.com/brewroot/packages/dpdk/17.11/6.el7fdb/x86_64/dpdk-tools-17.11-6.el7fdb.x86_64.rpm
RPM_DRIVERCTL=http://download-node-02.eng.bos.redhat.com/brewroot/packages/driverctl/0.95/1.el7fdparch/noarch/driverctl-0.95-1.el7fdparch.noarch.rpm

Comment 2 Marcelo Ricardo Leitner 2018-04-26 16:30:57 UTC
Did you enable hugepages in the guest?

Comment 3 qding 2018-04-27 01:13:24 UTC
(In reply to Marcelo Ricardo Leitner from comment #2)
> Did you enable hugepages in the guest?

Yes, the trace below excerpted from the beaker job

[root@localhost ~]# grep -i huge /proc/meminfo
Anon[01;31m[KHuge[m[KPages:     26624 kB
[01;31m[KHuge[m[KPages_Total:       1
[01;31m[KHuge[m[KPages_Free:        1
[01;31m[KHuge[m[KPages_Rsvd:        0
[01;31m[KHuge[m[KPages_Surp:        0
[01;31m[KHuge[m[Kpagesize:    1048576 kB
[root@localhost ~]# echo $?
0

Comment 4 Marcelo Ricardo Leitner 2018-04-27 14:50:57 UTC
You mentioned the card under test is 10Gbps:

[root@dell-per730-04 ~]# lspci -m -s 0000:04:00.0
04:00.0 ... "ConnectX-4 Lx Stand-up dual-port 10GbE MCX4121A-XCAT"

But the tests are performing higher than that:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2018/04/24431/2443129/5073845/71093363/TESTOUT.log
running trial 001, rate 24.000000
cmd: python trex-txrx.py ... frame_size='64', ... rate=24.0, rate_unit='mpps', ....

For 10GbE it should be at most 14.4Mpps.


Is the test doing some sort of warm-up period, for then measuring packet drops?
You're using 1k flows and with OVS Offloading, the process of learning a new flow is considerably slower. That said, it is expected that some loss at the beginning of the test will happen.

Comment 5 qding 2018-04-28 03:26:47 UTC
(In reply to Marcelo Ricardo Leitner from comment #4)
> 
> For 10GbE it should be at most 14.4Mpps.

After change the starting rate to 14.4, the result is a bit of better, but still not so good. Please see the log below.

> 
> 
> Is the test doing some sort of warm-up period, for then measuring packet
> drops?
> You're using 1k flows and with OVS Offloading, the process of learning a new
> flow is considerably slower. That said, it is expected that some loss at the
> beginning of the test will happen.


I'm afraid not do the warm-up. I'm using binary-search.py from https://github.com/atheurer/trafficgen, but have no idea how to do it. I'll try to figure it out.


running trial 001, rate 14.400000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 40.889866%, lost packets: 176644213)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 48.951702%, lost packets: 14686)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 37.490327%, lost packets: 161958204)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 47.655078%, lost packets: 14297)
running trial 002, rate 7.200000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 15.561260%, lost packets: 33612321)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 15.649478%, lost packets: 4695)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 10.876432%, lost packets: 23493094)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 10.546315%, lost packets: 3164)
running trial 003, rate 3.600000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000773%, lost packets: 835)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.033429%, lost packets: 36103)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.006666%, lost packets: 2)
running trial 004, rate 1.800000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000500%, lost packets: 270)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 005, rate 0.900000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000074%, lost packets: 20)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 006, rate 0.720000
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 007, rate 0.810000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000012%, lost packets: 3)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000041%, lost packets: 10)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 008, rate 0.765000
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 009, rate 0.787500
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000114%, lost packets: 9)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 010, rate 0.748125
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 011, rate 0.767813
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
===============================================
rx_pps when loss=0.0
    "rx_pps": 766056.1863758774,
    "rx_pps": 766056.1863758774,
rx_pps_total=1532112.3727517548
===============================================

Comment 6 qding 2018-04-28 07:58:37 UTC
Hi Marcelo,

Finally I solved the mystery. The problem is in my script. It's too fast to start binary-search after start t-rex server. Now the result seems good. I close the bug.

Thank you.


===============================================
grep -e 'running trial' -e 'percent loss' /tmp/binary_search.log
running trial 001, rate 14.400000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 7.037941%, lost packets: 30403905)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 37.925402%, lost packets: 11378)
(trial failed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 6.503911%, lost packets: 28096897)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 37.135429%, lost packets: 11141)
running trial 002, rate 7.200000
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 003, rate 10.800000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000094%, lost packets: 303)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 12.430000%, lost packets: 3729)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial failed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 18.366667%, lost packets: 5510)
running trial 004, rate 9.000000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000047%, lost packets: 127)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 005, rate 8.100000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000018%, lost packets: 44)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 006, rate 7.650000
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000013%, lost packets: 29)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 007, rate 7.267500
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000013%, lost packets: 29)
(trial failed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.003333%, lost packets: 1)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 008, rate 6.904125
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 009, rate 7.085813
(trial failed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000004%, lost packets: 3)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 010, rate 6.731522
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
running trial 011, rate 6.908667
(trial passed requirement, percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 0 -> 1, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
(trial passed requirement, latency percent loss, device pair: 1 -> 0, requested: 0.000000%, achieved: 0.000000%, lost packets: 0)
===============================================
rx_pps when loss=0.0
    "rx_pps": 6895643.298502119,
    "rx_pps": 6895643.298502119,
rx_pps_total=13791286.597004238
===============================================


Note You need to log in before you can comment on or make changes to this bug.