From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>
Subject: Re: [dts] [PATCH] tests/nic_single_core_perf: add broadcom nic support
Date: Thu, 22 Jul 2021 14:34:07 -0400 [thread overview]
Message-ID: <CAHx6DYAd=m0qrmckGOXB4f8EdfGsroz3Lp1qiFdvOs3sXOoGtg@mail.gmail.com> (raw)
In-Reply-To: <20210714174756.38730-1-ohilyard@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
Hello Lijuan,
I just wanted to follow up and ask about the status of this patch. I would
like to minimize the time the community lab is running patches that are not
in mainline DTS.
Owen
On Wed, Jul 14, 2021 at 1:47 PM <ohilyard@iol.unh.edu> wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> Add support for brcm_P2100G and brcm_57414 to nic_single_core_perf.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
> tests/TestSuite_nic_single_core_perf.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_nic_single_core_perf.py
> b/tests/TestSuite_nic_single_core_perf.py
> index dee189e5..4ccc04ac 100644
> --- a/tests/TestSuite_nic_single_core_perf.py
> +++ b/tests/TestSuite_nic_single_core_perf.py
> @@ -54,7 +54,8 @@ class TestNicSingleCorePerf(TestCase):
> PMD prerequisites.
> """
> self.verify(self.nic in ['niantic', 'fortville_25g',
> 'fortville_spirit', 'ConnectX5_MT4121',
> - 'ConnectX4_LX_MT4117',
> 'columbiaville_100g', 'columbiaville_25g', 'columbiaville_25gx2'],
> + 'ConnectX4_LX_MT4117',
> 'columbiaville_100g', 'columbiaville_25g', 'columbiaville_25gx2',
> + 'brcm_57414', 'brcm_P2100G'],
> "Not required NIC ")
> self.headers_size = HEADER_SIZE['eth'] + HEADER_SIZE['ip']
>
> --
> 2.30.2
>
>
[-- Attachment #2: Type: text/html, Size: 2197 bytes --]
next prev parent reply other threads:[~2021-07-22 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 17:47 ohilyard
2021-07-22 18:34 ` Owen Hilyard [this message]
2021-07-26 1:55 ` 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='CAHx6DYAd=m0qrmckGOXB4f8EdfGsroz3Lp1qiFdvOs3sXOoGtg@mail.gmail.com' \
--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).