From: Ali Alnubani <alialnu@mellanox.com>
To: dts@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: [dts] [PATCH for-next v2 0/3] nic_single_core_perf: add support for Mellanox's nics
Date: Fri, 30 Mar 2018 02:47:41 +0300 [thread overview]
Message-ID: <20180329234744.17716-1-alialnu@mellanox.com> (raw)
This patchset adds support to run nic_single_core_perf test on
ConnectX-5 EX, ConnectX-4 LX 25G, and ConnectX-4 LX 40G.
Please note that this series is applied on top of
Patrick's "Fixes and modifications for T-Rex integration and nic_single_core_perf"
patchset: http://dpdk.org/ml/archives/dts/2018-March/003893.html
Ali Alnubani (3):
framework/project_dpdk: pass modprobe if driver is mlx5_core
nics/net_device: add a function to get nic speed
nic_single_core_perf: add support for Mellanox's nics
Changes in v2:
- Fixed handling an exception in get_nic_speed function.
conf/nic_single_core_perf.cfg | 3 +++
framework/project_dpdk.py | 5 ++++-
nics/net_device.py | 14 ++++++++++++++
tests/TestSuite_nic_single_core_perf.py | 25 ++++++++++++++++++++++++-
4 files changed, 45 insertions(+), 2 deletions(-)
--
2.16.2
next reply other threads:[~2018-03-29 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 23:47 Ali Alnubani [this message]
2018-03-29 23:47 ` [dts] [PATCH for-next v2 1/3] framework/project_dpdk: pass modprobe if driver is mlx5_core Ali Alnubani
2018-03-29 23:47 ` [dts] [PATCH for-next v2 2/3] nics/net_device: add a function to get nic speed Ali Alnubani
2018-03-30 8:29 ` Liu, Yong
2018-03-30 22:55 ` Ali Alnubani
2018-03-29 23:47 ` [dts] [PATCH for-next v2 3/3] nic_single_core_perf: add support for Mellanox's nics Ali Alnubani
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=20180329234744.17716-1-alialnu@mellanox.com \
--to=alialnu@mellanox.com \
--cc=dpdklab@iol.unh.edu \
--cc=dts@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).