From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>
Subject: [dts] Question about config file handling for DTS
Date: Fri, 21 May 2021 13:47:57 -0400 [thread overview]
Message-ID: <CAHx6DYBCX6AXwMPEiNfoPcq071y-Dxrz27sHkNF1FG5jQoCv_w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
I've been spending a lot of time working with the DTS config files
recently, and I noticed that the ports config is only linked to a CRB via
expecting the IP address of the DUT to be a section in the ports config
file. Is there a reason for this behavior? It seems to me like it would
make more sense to have the CRB config file specify the name of an entry in
the ports config file.
This is mostly a workaround for many of the functional tests not running
when performance testing is turned on. The community lab currently
maintains two DTS installations on the tester side-by-side to get around
this problem, but fixing this seems like it would allow the community lab
to use a single DTS installation per tester, greatly easing
automated deployment.
[-- Attachment #2: Type: text/html, Size: 799 bytes --]
reply other threads:[~2021-05-21 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHx6DYBCX6AXwMPEiNfoPcq071y-Dxrz27sHkNF1FG5jQoCv_w@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).