Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seeing ierrors in Stats When Running in STL Mode #3

Open
jeremy020 opened this issue Jul 19, 2022 · 1 comment
Open

Seeing ierrors in Stats When Running in STL Mode #3

jeremy020 opened this issue Jul 19, 2022 · 1 comment

Comments

@jeremy020
Copy link

Description

While using trex with STL mode, I noticed that they are a lot of ierrors in the stats outputted by trex, and this has an impact on the over all performance of trex application in STL mode.

TRex configuration

interfaces: ['0000:14:00.0', '0000:15:00.0']
  rx_desc: 4096
  port_info:
      - ip: 1.1.1.1
        default_gw: 2.2.2.2
      - ip: 2.2.2.2
        default_gw: 1.1.1.1
  platform:
      master_thread_id: 0
      latency_thread_id: 10
      dual_if:
        - socket: 0
          threads: [1,2,3,4,5,6,7,8,9,20,21,22,23,24,25,26,27,28,29]

Screenshots

Screen Shot 2022-07-19 at 3 27 45 PM

To Reproduce

  1. Start trex on one terminal by using ./t-rex-64 -c 10 -i
  2. Start trex-console on another terminal using ./trex-console
  3. Then using this command start -f stl/udp_1pkt_simple.py -m 10000000 -d 100 -p 0 in trex-console
@jeremy020 jeremy020 changed the title Seeing ierrors in Stats When Running in STL Mode Seeing **ierrors** in Stats When Running in STL Mode Jul 19, 2022
@jeremy020 jeremy020 changed the title Seeing **ierrors** in Stats When Running in STL Mode Seeing *ierrors* in Stats When Running in STL Mode Jul 19, 2022
@jeremy020 jeremy020 changed the title Seeing *ierrors* in Stats When Running in STL Mode Seeing ierrors in Stats When Running in STL Mode Jul 19, 2022
@akshaydorwat
Copy link
Collaborator

akshaydorwat commented Mar 17, 2023

RX vlan packet filter capability is missing on the IONIC DPDK Driver. Hence packets which are supposed to be dropped in HW, are pushed to the buffer ring, which is not drained by the Trex application, as it is not interested in these packet at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants