From: ohilyard@iol.unh.edu
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [dts] [PATCH] framework/settings: Add broadcom nics to dts
Date: Wed, 14 Jul 2021 12:22:10 -0400 [thread overview]
Message-ID: <20210714162210.30697-1-ohilyard@iol.unh.edu> (raw)
From: Owen Hilyard <ohilyard@iol.unh.edu>
brcm_57414 and brcm_P2100G are not currently in the settings files for
DTS. This causes errors when DTS is run with these nics. The community
lab was running a patched version of DTS, but we are making an effort to
more closely align to upstream. Since these nics are used in CI for
DPDK, they are well tested with DTS and shouldn't cause any issues.
Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
---
conf/nic_single_core_perf.cfg | 8 +++++++-
framework/settings.py | 8 ++++++--
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/conf/nic_single_core_perf.cfg b/conf/nic_single_core_perf.cfg
index 7970995e..4a1073f5 100644
--- a/conf/nic_single_core_perf.cfg
+++ b/conf/nic_single_core_perf.cfg
@@ -72,4 +72,10 @@ expected_throughput = {
'1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}}},
'ConnectX5_MT4121': {
'1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
- '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}}}
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}},
+ 'brcm_57414': {
+ '1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}},
+ 'brcm_P2100G': {
+ '1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}}}
\ No newline at end of file
diff --git a/framework/settings.py b/framework/settings.py
index 9ceffe2e..fe7c01b5 100644
--- a/framework/settings.py
+++ b/framework/settings.py
@@ -110,7 +110,9 @@ NICS = {
'fastlinq_ql41000_vf': '1077:8090',
'carlsville': '8086:15ff',
'hi1822': '19e5:1822',
- 'foxville': '8086:15f2'
+ 'foxville': '8086:15f2',
+ 'brcm_57414': '14e4:16d7',
+ 'brcm_P2100G': '14e4:1750'
}
DRIVERS = {
@@ -174,7 +176,9 @@ DRIVERS = {
'fastlinq_ql41000_vf': 'qede',
'carlsville': 'i40e',
'hi1822': 'hinic',
- 'foxville':'igc'
+ 'foxville':'igc',
+ 'brcm_57414': 'bnxt_en',
+ 'brcm_P2100G': 'bnxt_en'
}
"""
--
2.30.2
next reply other threads:[~2021-07-14 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:22 ohilyard [this message]
2021-07-22 18:34 ` Owen Hilyard
2021-07-26 1:54 ` Tu, Lijuan
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=20210714162210.30697-1-ohilyard@iol.unh.edu \
--to=ohilyard@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
/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).