>This table should be const, and is the same CRC32 as implemented alread> in
>lib/hash/rte_crc ?
Hi Stepen,
The table and CRC32 as implemented already in lib/hash/rte_crc are
different.The table is calculated by build_crc8_table in app/test/test_atomic.c
Thanks
李晗晓
IT开发工程师
RCH八部/无线及算力研究院/无
Introduce driver support for ZSDA which can
help to accelerate storage data process.
Signed-off-by: Hanxiao Li
---
MAINTAINERS | 4 +
config/rte_config.h | 4 +
drivers/common/zsda/zsda_common.c | 168 +++
drivers/common/zsda/zsda_common.h | 32
Add queue initialization, release, enqueue, dequeue and other interface.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/zsda_qp.c | 720 ++
drivers/common/zsda/zsda_qp.h | 163
2 files changed, 883 insertions(+)
create mode 100644 drivers/common/zsda/
Add support for zsdadev operations such as dev_start and dev_stop.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/zsda_device.c | 476 ++
drivers/common/zsda/zsda_device.h | 103 +++
2 files changed, 579 insertions(+)
create mode 100644 drivers/common/zsda/zsd
Add zsda compressdev driver and enqueue, dequeue interface.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 25 ++
drivers/compress/zsda/zsda_comp.c | 320 ++
drivers/compress/zsda/zsda_comp.h | 27 ++
drivers/compress/zsda/zsda_comp_pmd.c | 453 ++
On 8/20/2024 5:59 PM, Robin Jarry wrote:
Anatoly Burakov, Aug 20, 2024 at 17:35:
Update coding style:
- make it PEP-484 compliant
- address all flake8, mypy etc. warnings
- use f-strings in place of old-style string interpolation
- refactor printing to make the code more readable
- read valid C
On 8/20/2024 9:22 PM, Robin Jarry wrote:
Anatoly Burakov, Aug 20, 2024 at 17:35:
In traditional NUMA case, NUMA nodes and physical sockets were used
interchangeably, but there are cases where there can be multiple NUMA
nodes per socket, as well as all CPU's being assigned NUMA node 0 even in
cas
On 8/20/2024 5:57 PM, Robin Jarry wrote:
Anatoly Burakov, Aug 20, 2024 at 17:35:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Use quotes consistently
- Address all Python static analysis (e.g. mypy, pylint) warnings
On 8/20/2024 5:52 PM, Stephen Hemminger wrote:
On Tue, 20 Aug 2024 16:35:16 +0100
Anatoly Burakov wrote:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Use quotes consistently
- Address all Python static analysis (e.
On 8/21/2024 10:52 AM, Burakov, Anatoly wrote:
On 8/20/2024 5:57 PM, Robin Jarry wrote:
Anatoly Burakov, Aug 20, 2024 at 17:35:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Use quotes consistently
- Address all Pyth
On 8/21/2024 11:06 AM, Burakov, Anatoly wrote:
On 8/21/2024 10:52 AM, Burakov, Anatoly wrote:
On 8/20/2024 5:57 PM, Robin Jarry wrote:
Anatoly Burakov, Aug 20, 2024 at 17:35:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywh
In traditional NUMA case, NUMA nodes and physical sockets were used
interchangeably, but there are cases where there can be multiple NUMA
nodes per socket, as well as all CPU's being assigned NUMA node 0 even in
cases of multiple sockets. Use sysfs to print out NUMA information.
Signed-off-by: Ana
Currently, devbind does not print out any NUMA information, which makes
figuring out which NUMA node device belongs to not trivial. Add printouts
for NUMA information if NUMA support is enabled on the system.
Signed-off-by: Anatoly Burakov
Acked-by: Robin Jarry
---
Notes:
v1 -> v2:
- Ad
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Address all Python static analysis (e.g. mypy, pylint) warnings
- Format code with Ruff
- Improve error handling
- Refactor printing and sysfs/procfs access functions
- Sort
Burakov, Anatoly, Aug 21, 2024 at 11:16:
> Actually, I take that back - I had a configuration mishap and didn't
> notice that I wasn't using Ruff for formatting on the machine I was
> creating the commits.
>
> Still, cpu_layout's formatting is not affected, but hugepage script is.
>
> However,
Update coding style:
- make it PEP-484 compliant
- address all flake8, mypy etc. warnings
- use f-strings in place of old-style string interpolation
- refactor printing to make the code more readable
- read valid CPU ID's from "online" sysfs node
Signed-off-by: Anatoly Burakov
---
Notes:
v3
Anatoly Burakov, Aug 21, 2024 at 11:22:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Address all Python static analysis (e.g. mypy, pylint) warnings
- Format code with Ruff
- Improve error handling
- Refactor printing
On 8/21/2024 11:26 AM, Robin Jarry wrote:
Anatoly Burakov, Aug 21, 2024 at 11:22:
Update coding style:
- Make the code PEP-484 compliant
- Add more comments, improve readability, use f-strings everywhere
- Address all Python static analysis (e.g. mypy, pylint) warnings
- Format code with Ruff
-
Update coding style:
- make it PEP-484 compliant
- format code with Ruff
- address all mypy etc. warnings
- use f-strings in place of old-style string interpolation
- refactor printing to make the code more readable
- read valid CPU ID's from "online" sysfs node
Signed-off-by: Anatoly Burakov
--
In traditional NUMA case, NUMA nodes and physical sockets were used
interchangeably, but there are cases where there can be multiple NUMA
nodes per socket, as well as all CPU's being assigned NUMA node 0 even in
cases of multiple sockets. Use sysfs to print out NUMA information.
Signed-off-by: Ana
Update coding style:
- make the code PEP-484 compliant
- add more comments, improve readability, use f-strings everywhere
- address all Python static analysis (e.g. mypy, pylint) warnings
- format code with Ruff
- improve error handling
- refactor printing and sysfs/procfs access functions
- sort
Currently, devbind does not print out any NUMA information, which makes
figuring out which NUMA node device belongs to not trivial. Add printouts
for NUMA information if NUMA support is enabled on the system.
Signed-off-by: Anatoly Burakov
Acked-by: Robin Jarry
---
Notes:
v1 -> v2:
- Ad
Anatoly Burakov, Aug 21, 2024 at 11:44:
Update coding style:
- make it PEP-484 compliant
- format code with Ruff
- address all mypy etc. warnings
- use f-strings in place of old-style string interpolation
- refactor printing to make the code more readable
- read valid CPU ID's from "online" sysf
https://bugs.dpdk.org/show_bug.cgi?id=1525
Bug ID: 1525
Summary: dpdk mempool creation is resulting into lot of memory
getting wasted
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status:
Anatoly Burakov, Aug 21, 2024 at 11:44:
Update coding style:
- make the code PEP-484 compliant
- add more comments, improve readability, use f-strings everywhere
- address all Python static analysis (e.g. mypy, pylint) warnings
- format code with Ruff
- improve error handling
- refactor printing
Anatoly Burakov, Aug 21, 2024 at 11:44:
In traditional NUMA case, NUMA nodes and physical sockets were used
interchangeably, but there are cases where there can be multiple NUMA
nodes per socket, as well as all CPU's being assigned NUMA node 0 even in
cases of multiple sockets. Use sysfs to print
Anatoly Burakov, Aug 21, 2024 at 11:44:
Currently, devbind does not print out any NUMA information, which makes
figuring out which NUMA node device belongs to not trivial. Add printouts
for NUMA information if NUMA support is enabled on the system.
Signed-off-by: Anatoly Burakov
Acked-by: Robin
Not really needed, check out the main branch can avoid such issue. Thanks for
looking into this.
From: Stephen Hemminger
Sent: Friday, August 16, 2024 12:32 AM
To: NBU-Contact-Thomas Monjalon (EXTERNAL)
Cc: Christian Ehrhardt ; bl...@debian.org
; ktray...@redhat
Goal of the patch series is to improve SSE macswap on x86_64 by
reducing the stalls in backend engine. Original implementation of
the SSE-mac-swap makes loop call to multiple load, shuffle & store.
Using SIMD ISA interleaving, register variable and reducing L1 & L2
cache eviction, we can reduce th
Currently SSE SIMD variables are declared as stack variables. Allowing
the use of keyword register for shuffle mask and address variables,
improves the mac-swap Mpps by 1 for single queue.
Test Result:
* Platform: AMD EPYC 9554 @3.1GHz, no boost
* Test scenarios: TEST-PMD 64B IO vs MAC-SWAP
* N
Interleaving SSE SIMD load, shuffle, and store, helps to
improve the overall mac-swapp Mpps for both RX and TX.
Test Result:
* Platform: AMD EPYC 9554 @3.1GHz, no boost
* Test scenarios: TEST-PMD 64B IO vs MAC-SWAP
* NIC: broadcom P2100: loopback 2*100Gbps
--
Moving the offload flag update from end to start of the loop,
helps to reduce L1 or L2 cache evictions and amortize shuffle.
This helps to improve RX packet in mac-swap processing.
Test Result:
* Platform: AMD EPYC 9554 @3.1GHz, no boost
* Test scenarios: TEST-PMD 64B IO vs MAC-SWAP
* NIC: broa
The device_error_handling_mode of testpmd port may not be present, e.g.
in VM ports.
Fixes: 61d5bc9bf974 ("dts: add port info command to testpmd shell")
Signed-off-by: Juraj Linkeš
---
dts/framework/remote_session/testpmd_shell.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Add an automated way to gather available capabilities of the tested
hardware and skip test suites or cases which require capabilities that
are not available.
This is done through two decorators:
1. The first marks a test suite method as test case. This populates the
default attributes of each t
Regular Python enumerations create only one instance for members with
the same value, such as:
class MyEnum(Enum):
foo = 1
bar = 1
MyEnum.foo and MyEnum.bar are aliases that return the same instance.
DTS needs to return different instances in the above scenario so that we
can map capabili
Add decorators for functional and performance test cases. These
decorators add attributes to the decorated test cases.
With the addition of decorators, we change the test case discovery
mechanism from looking at test case names according to a regex to simply
checking an attribute of the function a
If a test case is not relevant to the testing environment (such as when
a NIC doesn't support a tested feature), the framework should skip it.
The mechanism is a skeleton without actual logic that would set a test
case or suite to be skipped.
The mechanism uses a protocol to extend test suites and
We currently assume there are two links between the SUT and TG nodes,
but that's too strict, even for some of the already existing test cases.
Add support for topologies with less than two links.
For topologies with no links, dummy ports are used. The expectation is
that test suites or cases that
A test case or suite may require certain capabilities to be present in
the tested environment. Add the basic infrastructure for checking the
support status of capabilities:
* The Capability ABC defining the common capability API
* Extension of the TestProtocol with required capabilities (each test
When using port information multiple times in a testpmd shell instance
lifespan, it's desirable to not get the information each time, so
caching is added. In case the information changes, there's a way to
force the update.
Signed-off-by: Juraj Linkeš
---
dts/framework/remote_session/testpmd_shel
Some test cases or suites may be testing a NIC feature that is not
supported on all NICs, so add support for marking test cases or suites
as requiring NIC capabilities.
The marking is done with a decorator, which populates the internal
required_capabilities attribute of TestProtocol. The NIC capab
Add support for marking test cases as requiring a certain topology. The
default topology is a two link topology and the other supported
topologies are one link and no link topologies.
The TestProtocol of test suites and cases is extended with the topology
type each test suite or case requires. Eac
Add new files to generate DTS API documentation from.
Signed-off-by: Juraj Linkeš
---
doc/api/dts/framework.testbed_model.capability.rst | 6 ++
doc/api/dts/framework.testbed_model.rst| 2 ++
doc/api/dts/framework.testbed_model.topology.rst | 6 ++
3 files changed, 14 inser
The scatter Rx offload capability is needed for the pmd_buffer_scatter
test suite. The command that retrieves the capability is:
show port rx_offload capabilities
The command also retrieves a lot of other capabilities (RX_OFFLOAD_*)
which are all added into a Flag. The Flag members correspond to
Add the capabilities advertised by the testpmd command "show port info"
so that test cases may be marked as requiring those capabilities:
RUNTIME_RX_QUEUE_SETUP
RUNTIME_TX_QUEUE_SETUP
RXQ_SHARE
FLOW_RULE_KEEP
FLOW_SHARED_OBJECT_KEEP
These names are copy pasted from the existing DeviceCapabilitiesF
On Thu, 15 Aug 2024 10:54:38 +0800
Hanxiao Li wrote:
> +uint16_t zsda_enqueue_op_burst(struct zsda_qp *qp, void **ops, const
> uint16_t nb_ops);
> +uint16_t zsda_dequeue_op_burst(struct zsda_qp *qp, void **ops, const
> uint16_t nb_ops);
> +
> +void tx_write_tail(struct zsda_queue *queue);
> +in
On Wed, 21 Aug 2024 20:08:55 +0530
Vipin Varghese wrote:
> diff --git a/app/test-pmd/macswap_sse.h b/app/test-pmd/macswap_sse.h
> index 223f87a539..29088843b7 100644
> --- a/app/test-pmd/macswap_sse.h
> +++ b/app/test-pmd/macswap_sse.h
> @@ -16,13 +16,13 @@ do_macswap(struct rte_mbuf *pkts[], uin
Address a few errors reported by Sphinx when generating documentation:
framework/params/__init__.py:docstring of framework.params.modify_str:3:
WARNING: Inline interpreted text or phrase reference start-string
without end-string.
framework/params/eal.py:docstring of framework.params.eal.Eal
The generation is done with Sphinx, which DPDK already uses, with
slightly modified configuration of the sidebar present in an if block.
DTS dependencies do not need to be installed, but there is the option to
install doc build dependencies with Poetry:
poetry install --with docs
The build itself
Sphinx imports every Python module (through the autodoc extension)
when generating documentation from docstrings, meaning all DTS
dependencies, including Python version, should be satisfied. This is not
a hard requirement, as imports from dependencies may be mocked in the
autodoc_mock_imports autod
When the DTS dependencies are not installed when building DTS API
documentation, the or operator produces errors when used with types from
those libraries:
autodoc: failed to import module 'remote_session' from module
'framework'; the following exception was raised:
Traceback (most recent call last
These sources could be generated with the sphinx-apidoc utility, but
that doesn't give us enough flexibility, such as sorting the order of
modules or changing the headers of the modules.
The sources included in this patch were in fact generated by said
utility, but modified to improve the look of
The tool used to generate DTS API docs is Sphinx, which is already in
use in DPDK. The same configuration is used to preserve style with one
DTS-specific configuration (so that the DPDK docs are unchanged) that
modifies how the sidebar displays the content. There's other Sphinx
configuration relate
On Wed, Aug 21, 2024 at 11:03 AM Juraj Linkeš
wrote:
> The tool used to generate DTS API docs is Sphinx, which is already in
> use in DPDK. The same configuration is used to preserve style with one
> DTS-specific configuration (so that the DPDK docs are unchanged) that
> modifies how the sidebar
This patch adds the required functionality for the RSS key_update,
RETA, and hash test suites. This includes:
The setting of custom RETA values for routing packets to specific
queues.
The setting of the RSS mode on all ports, to specify how to hash
the packets.
The updating of the RSS hash key used
---
v2:
* added filter for verbose output using dst mac address
Dean Marx (2):
dts: add csum HW offload to testpmd shell
dts: checksum offload test suite
dts/framework/config/conf_yaml_schema.json| 3 +-
dts/framework/remote_session/testpmd_shell.py | 124
dts/tests/TestSu
add csum_set_hw method to testpmd shell class. Port over
set_verbose and port start/stop from queue start/stop suite.
Signed-off-by: Dean Marx
---
dts/framework/remote_session/testpmd_shell.py | 124 ++
1 file changed, 124 insertions(+)
diff --git a/dts/framework/remote_session/
test suite for verifying layer 3/4 checksum offload
features on poll mode driver.
Depends-on: patch-143033
("dts: add text parser for testpmd verbose output")
Depends-on: patch-142691
("dts: add send_packets to test suites and rework packet addressing")
Signed-off-by: Dean Marx
---
dts/framewor
Hi everyone,
As discussed recently [1], here is a first draft of the IPv6 APIs rework. The
API change was announced before the 24.07 release [2]. This series is intended
for 24.11.
[1] http://inbox.dpdk.org/dev/d2sr8t1h39cj.jrqfi6jeh...@redhat.com/
[2]
https://git.dpdk.org/dpdk/commit/?id=835d4c
The checksum functions are used by both ipv4 and ipv6 functions. In
preparation of moving ipv6 symbols to a new header, move the checksum
related symbols to another dedicated header.
Signed-off-by: Robin Jarry
---
lib/net/meson.build | 1 +
lib/net/rte_cksum.h | 189 +++
There is currently no structure defined for IPv6 addresses. Introduce
one that is simply a uint8_t array of 16 elements without any union. The
idea is to ensure this structure alignment is 1 so that it can be mapped
directly on unaligned packet memory.
Signed-off-by: Robin Jarry
---
lib/net/rte_
Move all ipv6 related symbols to a dedicated header. Update all code
accordingly.
Signed-off-by: Robin Jarry
---
app/test/packet_burst_generator.c | 1 +
app/test/test_cryptodev_security_ipsec.c| 1 +
drivers/common/cnxk/cnxk_security.c | 1 +
drivers/crypto/cnxk/cn9k
The rte_ipv6_hdr uses ad-hoc uint8_t[16] arrays to represent addresses.
Replace these arrays with the previously introduced rte_ipv6_addr
structure. Adapt all code accordingly.
Signed-off-by: Robin Jarry
---
app/test-flow-perf/items_gen.c | 4 +--
app/test-pipeline/pipeline_hash.c
Add utility functions that use the previously introduced IPv6 address
structure. Add basic unit tests to ensure everything works as expected.
These functions will be used in the next commits to replace private
and/or duplicated functions.
Signed-off-by: Robin Jarry
---
app/test/meson.build
Replace duplicated and/or private functions by some of the previously
introduced utility functions.
Mark rib6 functions that deal with ipv6 addresses as deprecated.
Signed-off-by: Robin Jarry
---
app/test/test_fib6.c | 9 +++--
app/test/test_rib6.c | 2 +-
ex
Replace ad-hoc uint8_t[16] arrays with the previously introduced IPv6
address structure.
Signed-off-by: Robin Jarry
---
app/graph/ethdev.c | 40 ++-
app/graph/ethdev.h | 9 ---
app/graph/ip6_route.c | 47 +--
Update tcp6_flow_key to use the recently introduced IPv6 address
structure instead of uint8_t[16] arrays.
Signed-off-by: Robin Jarry
---
lib/gro/gro_tcp6.c | 8
lib/gro/gro_tcp6.h | 6 --
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/lib/gro/gro_tcp6.c b/lib/gro/gro
Update rte_ipv6_tuple to use the recently added IPv6 address structure
instead of uint8_t[16] arrays.
Signed-off-by: Robin Jarry
---
app/test/test_thash.c | 46 ---
lib/hash/rte_thash.h | 20 +--
2 files changed, 27 insertions(+), 39 delet
Update rte_ipsec_sadv6_key to use the recently introduced IPv6 address
structure instead of ad-hoc uint8_t[16] arrays.
Signed-off-by: Robin Jarry
---
app/test-sad/main.c| 24 ++---
app/test/test_ipsec_sad.c | 44 +++---
examples/ipsec-secg
Replace all address size and max depth macros with common ones from
rte_ip6.h.
Signed-off-by: Robin Jarry
---
app/test/test_fib6.c | 50 ++--
lib/fib/rte_fib6.c | 6 +++---
lib/fib/rte_fib6.h | 4
lib/fib/trie.c | 6 +++---
lib/fib/trie.h
Add more utilities to work with IPv6 addresses. These functions will be
required in order to help building IPv6 routing applications.
Signed-off-by: Robin Jarry
---
app/test/test_net_ipv6.c | 74 ++
lib/net/rte_ip6.h| 98 +++
Update rte_table_action_ipv6_header and rte_table_action_nat_params to
use the recently added IPv6 address structure instead of uint8_t[16]
arrays.
Signed-off-by: Robin Jarry
---
examples/ip_pipeline/cli.c | 12 +--
lib/pipeline/rte_table_action.c | 36 +-
Update rte_flow_tunnel, rte_flow_action_set_ipv6,
rte_flow_item_icmp6_nd_na and rte_flow_item_icmp6_nd_ns to use the
recently introduced IPv6 address structure instead of uint8_t[16]
arrays.
Update all code accordingly.
Signed-off-by: Robin Jarry
---
app/test-flow-perf/actions_gen.c |
Series to rework how testbed topologies are defined within the dts
configuration. Bugzilla ID 1360 originally asked for a rework to
define physical NIC devices on nodes. However, defining testbeds
purely by device negates the ability to create specific, multi-device
testers running performance test
The current design requires that a peer pci port is identified so that
test suites can create the correct port links. While this can work, it
also creates a lot of room for user error. Instead, devices should be
given a unique identifier which is referenced in defined test runs.
Both defined testb
In order to leverage the usability of unique identifiers on ports, the
testbed_model Port object needs some refactoring/trimming of obsolete or
needless attributes.
Bugzilla ID: 1478
Signed-off-by: Nicholas Pratte
---
dts/framework/testbed_model/port.py | 45 +++--
1 fil
The TestSuite object needs to access the running test run config in
order to identify the ports that need to be linked. To do this,
DTSRunner needs to be tweaked to accept test run configs to test suites,
and the TestSuite constructor needs to be reworked to accept test run
configs.
Bugzilla ID: 1
From: Jeremy Spewock
There currently is no method of creating or managing virtual functions
(VFs) in the new DTS framework but there are multiple test suites in
the old DTS framework that provide testing coverage using them. This
patch adds the functionality to the framework that is needed to cre
From: Jeremy Spewock
Previously the DTS framework only included methods that bind all ports
that the test run was aware of to either the DPDK driver or the OS
driver. There are however some cases, like creating virtual functions,
where you would want some ports bound to the OS driver and others b
From: Jeremy Spewock
Previously in the DTS framework the helper methods in the TestSutie
class designated ports as either ingress or egress ports and would wrap
the methods of the traffic generator to allow packets to only flow to
those designated ingress or egress ports. This is undesirable in s
From: Jeremy Spewock
Virtual functions in the framework are created using SR-IOV. The process
for doing this can vary depending on the operating system, so the
commands to create VFs have to be abstracted into different classes
based on the operating system. This patch adds the stubs for methods
From: Jeremy Spewock
In DPDK applications virtual functions are treated the same as ports,
but within the framework there are benefits to differentiating the two
in order to add more metadata to VFs about where they originate from.
For this reason this patch adds a new class for handling virtual
From: Jeremy Spewock
In order for test suites to create virtual functions there has to be
functions in the API that developers can use. This patch adds the
ability to create virtual functions to the Node API so that they are
reachable within test suites.
Bugzilla ID: 1500
Signed-off-by: Jeremy
From: Jeremy Spewock
v2:
* Accidentally left out a formatting fix in v1.
Jeremy Spewock (5):
dts: allow binding only a single port to a different driver
dts: parameterize what ports the TG sends packets to
dts: add class for virtual functions
dts: add OS abstractions for creating virtu
From: Jeremy Spewock
Previously the DTS framework only included methods that bind all ports
that the test run was aware of to either the DPDK driver or the OS
driver. There are however some cases, like creating virtual functions,
where you would want some ports bound to the OS driver and others b
From: Jeremy Spewock
Previously in the DTS framework the helper methods in the TestSutie
class designated ports as either ingress or egress ports and would wrap
the methods of the traffic generator to allow packets to only flow to
those designated ingress or egress ports. This is undesirable in s
From: Jeremy Spewock
In DPDK applications virtual functions are treated the same as ports,
but within the framework there are benefits to differentiating the two
in order to add more metadata to VFs about where they originate from.
For this reason this patch adds a new class for handling virtual
From: Jeremy Spewock
Virtual functions in the framework are created using SR-IOV. The process
for doing this can vary depending on the operating system, so the
commands to create VFs have to be abstracted into different classes
based on the operating system. This patch adds the stubs for methods
From: Jeremy Spewock
In order for test suites to create virtual functions there has to be
functions in the API that developers can use. This patch adds the
ability to create virtual functions to the Node API so that they are
reachable within test suites.
Bugzilla ID: 1500
Signed-off-by: Jeremy
From: Jeremy Spewock
v2:
* Accidentally left out a formatting fix in v1.
Jeremy Spewock (5):
dts: allow binding only a single port to a different driver
dts: parameterize what ports the TG sends packets to
dts: add class for virtual functions
dts: add OS abstractions for creating virtu
From: Jeremy Spewock
Previously the DTS framework only included methods that bind all ports
that the test run was aware of to either the DPDK driver or the OS
driver. There are however some cases, like creating virtual functions,
where you would want some ports bound to the OS driver and others b
From: Jeremy Spewock
Previously in the DTS framework the helper methods in the TestSutie
class designated ports as either ingress or egress ports and would wrap
the methods of the traffic generator to allow packets to only flow to
those designated ingress or egress ports. This is undesirable in s
From: Jeremy Spewock
In DPDK applications virtual functions are treated the same as ports,
but within the framework there are benefits to differentiating the two
in order to add more metadata to VFs about where they originate from.
For this reason this patch adds a new class for handling virtual
From: Jeremy Spewock
Virtual functions in the framework are created using SR-IOV. The process
for doing this can vary depending on the operating system, so the
commands to create VFs have to be abstracted into different classes
based on the operating system. This patch adds the stubs for methods
From: Jeremy Spewock
In order for test suites to create virtual functions there has to be
functions in the API that developers can use. This patch adds the
ability to create virtual functions to the Node API so that they are
reachable within test suites.
Bugzilla ID: 1500
Signed-off-by: Jeremy
Apologies for sending out the v2 twice for this series, when I
attempted the first time the reply chain broke somehow and patchwork
didn't consider all the patches as one series. This should be fixed
now.
From: Pavan Nikhilesh
In OP_FWD mode, if internal port is supported, the target event queue
should be the TEST_APP_EV_QUEUE_ID.
Fixes: a276e7c8fbb3 ("test/event: add DMA adapter auto-test")
Signed-off-by: Pavan Nikhilesh
---
app/test/test_event_dma_adapter.c | 5 -
1 file changed, 4 inser
From: Jeremy Spewock
rfc-v3:
* add missing depends-on tags to appropriate commits.
* adjust some other small issues in commit bodies
* add changes to fix name of function in os_udp
Jeremy Spewock (5):
dts: allow binding only a single port to a different driver
dts: parameterize what ports
From: Jeremy Spewock
Previously the DTS framework only included methods that bind all ports
that the test run was aware of to either the DPDK driver or the OS
driver. There are however some cases, like creating virtual functions,
where you would want some ports bound to the OS driver and others b
From: Jeremy Spewock
Previously in the DTS framework the helper methods in the TestSuite
class designated ports as either ingress or egress ports and would wrap
the methods of the traffic generator to allow packets to only flow to
those designated ingress or egress ports. This is undesirable in s
1 - 100 of 110 matches
Mail list logo
