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

Low TX rate with 512B frames #678

Closed
alialnu opened this issue Apr 13, 2021 · 7 comments
Closed

Low TX rate with 512B frames #678

alialnu opened this issue Apr 13, 2021 · 7 comments

Comments

@alialnu
Copy link

alialnu commented Apr 13, 2021

Starting from TRex v2.80, there is a ~50% drop in TX rate with 512B frames.

The issue can be reproduced with stl/bench.py.

To reproduce, start TRex:
$ ./t-rex-64 -i -c 14

Then start traffic and monitor stats:
> start -p 0 1 -m 100% -f stl/bench.py -t size=512,vm=cached

This was caused by dbb64b2, and the last good version is v2.79.

NIC: ConnectX-5.
Reproduces with multiple versions of MLNX_OFED (4.6-1.0.1.1, 5.2-2.2.0.0 and 5.3-1.0.0.1).

@hhaim
Copy link
Contributor

hhaim commented Apr 14, 2021

@alialnu This is a mlx5 driver/ofed issue. trex code is the same. could you check with latest DPDK version v2.89 and latest ofed?

@alialnu
Copy link
Author

alialnu commented Apr 14, 2021

@alialnu This is a mlx5 driver/ofed issue. trex code is the same. could you check with latest DPDK version v2.89 and latest ofed?

I can also reproduce with v2.89.

@hhaim
Copy link
Contributor

hhaim commented Apr 18, 2021

@alialnu it means that this is a dpdk mlx5 driver issue. try to figure out what was change betwean the DPDK. You can try to to git bisect to find the driver change that intruduce this.

@aleks-kozyrev
Copy link
Contributor

@hhaim could you please try adding "dpdk_devargs : ['txq_inline_min=1','txq_inline_max=700']" to your trex_cfg.yaml file.
This should restore the performance for 512 bytes traffic generation.

@alialnu
Copy link
Author

alialnu commented Jun 17, 2021

@hhaim could you please try adding "dpdk_devargs : ['txq_inline_min=1','txq_inline_max=700']" to your trex_cfg.yaml file.
This should restore the performance for 512 bytes traffic generation.

Thanks for the suggestion @aleks-kozyrev. I'll try it Do you have an example of how to add this modification to the file?

@alialnu
Copy link
Author

alialnu commented Jun 18, 2021

@hhaim could you please try adding "dpdk_devargs : ['txq_inline_min=1','txq_inline_max=700']" to your trex_cfg.yaml file.
This should restore the performance for 512 bytes traffic generation.

Thanks for the suggestion @aleks-kozyrev. I'll try it Do you have an example of how to add this modification to the file?

Setting the devargs improves the rate with 512B frames, but degrades it with lower frame sizes.

@hhaim
Copy link
Contributor

hhaim commented Jul 25, 2021

v2.91 solves this

@hhaim hhaim closed this as completed Jul 25, 2021
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

Successfully merging a pull request may close this issue.

3 participants