DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tomáš Ďurovec" <tomas.durovec@pantheon.tech>
To: dev@dpdk.org, Luca.Vizzarro@arm.com, probb@iol.unh.edu,
	npratte@iol.unh.edu, dmarx@iol.unh.edu
Cc: "Tomáš Ďurovec" <tomas.durovec@pantheon.tech>
Subject: [PATCH 0/7] DTS external DPDK build
Date: Fri, 27 Sep 2024 18:08:47 +0200	[thread overview]
Message-ID: <20240927160854.279253-1-tomas.durovec@pantheon.tech> (raw)

This patch series adds ability to use pre-build DPDK in various options of usage. User can specify 
this option from config file or cmd arguments/environment variables:
* The source of DPDK (tarball or tree),
* The build dir witch will be located in a subdirectory of DPDK tree root directory, otherwise will 
  be used build configuration from config file, 
* Location where the DPDK source will be stored either in SUT node or local filesystem.

Tomáš Ďurovec (7):
  dts: rename build target to DPDK build
  dts: one dpdk build per test run
  dts: fix remote session file transfer vars
  dts: add the ability to copy directories via remote
  dts: add support for externally compiled DPDK
  doc: update argument options for external DPDK build
  dts: remove git ref option

 doc/guides/tools/dts.rst                      |  18 +-
 dts/conf.yaml                                 |  17 +-
 dts/framework/config/__init__.py              | 140 ++++++-
 dts/framework/config/conf_yaml_schema.json    |  72 +++-
 dts/framework/config/types.py                 |  19 +-
 dts/framework/exception.py                    |   4 +-
 dts/framework/logger.py                       |   4 -
 dts/framework/remote_session/dpdk_shell.py    |   2 +-
 .../remote_session/remote_session.py          |  24 +-
 dts/framework/remote_session/ssh_session.py   |  18 +-
 dts/framework/runner.py                       | 139 ++-----
 dts/framework/settings.py                     | 200 +++++++---
 dts/framework/test_result.py                  | 124 ++----
 dts/framework/test_suite.py                   |   2 +-
 dts/framework/testbed_model/node.py           |  22 +-
 dts/framework/testbed_model/os_session.py     | 209 ++++++++--
 dts/framework/testbed_model/posix_session.py  | 141 ++++++-
 dts/framework/testbed_model/sut_node.py       | 366 ++++++++++++------
 dts/framework/utils.py                        | 164 ++++----
 dts/tests/TestSuite_smoke_tests.py            |   2 +-
 20 files changed, 1078 insertions(+), 609 deletions(-)

-- 
2.46.1


             reply	other threads:[~2024-09-27 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 16:08 Tomáš Ďurovec [this message]
2024-09-27 16:08 ` [PATCH 1/7] dts: rename build target to " Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 2/7] dts: one dpdk build per test run Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 3/7] dts: fix remote session file transfer vars Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 4/7] dts: add the ability to copy directories via remote Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 5/7] dts: add support for externally compiled DPDK Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 6/7] doc: update argument options for external DPDK build Tomáš Ďurovec
2024-09-27 16:08 ` [PATCH 7/7] dts: remove git ref option Tomáš Ďurovec

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=20240927160854.279253-1-tomas.durovec@pantheon.tech \
    --to=tomas.durovec@pantheon.tech \
    --cc=Luca.Vizzarro@arm.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=npratte@iol.unh.edu \
    --cc=probb@iol.unh.edu \
    /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).