DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1360] DTS Config improvements
Date: Wed, 10 Jan 2024 12:13:07 +0000	[thread overview]
Message-ID: <bug-1360-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1360

            Bug ID: 1360
           Summary: DTS Config improvements
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: dts
          Assignee: dev@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

We’re not using the arch, os and cpu options in build target config. These were
meant for cross compilation and we may not even use them in the future, so
remove them. 

Remove the use_first_core option in execution config and modify the logic as if
use_first_core=True if the lcore option is not set. Also  properly document
this (in code and docs) and also emit an info log when skipping the first core
and a warning when using the core (something like only do this if you know what
you’re doing).

There are a lot of supported devices in the schema, trim down.

We may also remove the OS/Arch config of SUT nodes, as we should be able to
discover that.

We may want to do additional config validation, as the schema doesn't cover
everything.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3284 bytes --]

                 reply	other threads:[~2024-01-10 12:13 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=bug-1360-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).