From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>
Subject: Re: [PATCH v1] tests/nic_single_core_perf: Initalize packet generator
Date: Tue, 18 Jan 2022 13:11:36 -0500 [thread overview]
Message-ID: <CAHx6DYCTvrOm=F118fQjcu_oP6GtWGaXdPASARvkVAPNkeS+yQ@mail.gmail.com> (raw)
In-Reply-To: <20220118163032.30837-1-ohilyard@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
After more testing, it seems like this causes issues for some Nics due to
various compatibility workarounds elsewhere in DTS. I'll submit a v2 once
I've found the root cause and a fix for it.
[-- Attachment #2: Type: text/html, Size: 242 bytes --]
next prev parent reply other threads:[~2022-01-18 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:30 ohilyard
2022-01-18 18:11 ` Owen Hilyard [this message]
2022-01-24 20:35 ` [PATCH v2] " ohilyard
2022-01-26 6:23 ` 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='CAHx6DYCTvrOm=F118fQjcu_oP6GtWGaXdPASARvkVAPNkeS+yQ@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).