DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wu, Xiaoban" <Xiaoban_Wu@student.uml.edu>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Interesting considerate but annoying behavior of MLX5 driver
Date: Thu, 26 Apr 2018 22:26:36 +0000	[thread overview]
Message-ID: <DM5PR02MB2523C02F1588E8D6CA0ECD58BC8E0@DM5PR02MB2523.namprd02.prod.outlook.com> (raw)

Dear All,


I have two Dell PowerEdge R740 servers A and B running with ubuntu 16.04, each one has a Mellanox MCX556A-ECAT NIC installed on the PCIe x16 slot. And, the two NICs are directly connected back to back with a copper cable.


On server A, it runs a RX program which runs a function to process and analyze the received packets. On server B, it runs a packet-gen program which generates and sends packets out. They are both compiled with dpdk-17.11


Now the interesting thing is that on server B, it is kind of smart and considerate enough to automatically adjust its TX throughput according to how fast server A processes the packets. If server A processes the packets faster, then server B sends packets with a higher throughput. Similarly, if server A processes the packets slower, then server B sends packets with a lower throughput. Please note that once the program on server B starts, it is never interrupted by any way.


However, I think the server B should send out the packets with a constant throughput no matter how fast server A processes the packets.


Does anybody else notice this interesting behavior of MLX5 driver? Can anybody help me disable this feature permanently? Thanks very much for your help.


Best wishes,

Xiaoban

             reply	other threads:[~2018-04-26 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 22:26 Wu, Xiaoban [this message]
2018-04-26 22:40 ` Stephen Hemminger
2018-04-27  1:29   ` Wu, Xiaoban
2018-05-02 10:13     ` Adrien Mazarguil

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=DM5PR02MB2523C02F1588E8D6CA0ECD58BC8E0@DM5PR02MB2523.namprd02.prod.outlook.com \
    --to=xiaoban_wu@student.uml.edu \
    --cc=users@dpdk.org \
    /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).