> -Original Message-
> From: Naga Harish K, S V
> Sent: Monday, February 3, 2025 10:08 AM
> To: Jerin Jacob ; Shijith Thotton ;
> dev@dpdk.org
> Cc: Pavan Nikhilesh Bhagavatula ; Pathak, Pravin
> ; Hemant Agrawal ;
> Sachin Saxena ; Mattias R_nnblom
> ; Liang Ma ;
> Mccarthy, Peter ; Va
On Tue, 21 Jan 2025 11:44:21 +0800
Junlong Wang wrote:
> insert port tables in host.
>
> Signed-off-by: Junlong Wang
> ---
> drivers/net/zxdh/meson.build | 1 +
> drivers/net/zxdh/zxdh_ethdev.c | 24 ++
> drivers/net/zxdh/zxdh_msg.c| 65
> drivers/net/zxdh/zxdh_msg.h| 72 ++
MSVC does not support inline assembly, which is used by the
implementation of rte_atomic128_cmp_exchange and is needed
by the C11 flavor of lib/stack.
A special implementation of rte_atomic128_cmp_exchange
compatible with MSVC is added to rte_stack_lf_c11.h. It uses an
intrinsic function when usin
In general, non-C11 atomics are not to be used with MSVC.
This patch skips the non-C11 atomic tests when using MSVC.
Signed-off-by: Andre Muezerie
---
app/test/test_atomic.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/app/test/test_atomic.c b/app/test/test_atomic.c
index db07159e81..3f
An implementation compatible with MSVC is provided for
atomic128_cmp_exchange in rte_stack_lf_c11.h.
Now that the issues preventing the code needed to build lib/stack
have been addressed, it can be enabled so that it also gets built
when using the MSVC compiler.
Signed-off-by: Andre Muezerie
---
Variable "success" was not being initialized and there was a code
path where the last do/while loop in __rte_stack_lf_pop_elems
looked at the value of this variable before it was set to any.
Compiling with msvc resulted in stack_lf_autotest sometimes crashing.
The fix is to initialize the variabl
> From: Stephen Hemminger
> Sent: Wednesday, January 29, 2025 7:59 PM
> To: Long Li
> Cc: lon...@linuxonhyperv.com; Ferruh Yigit ; Andrew
> Rybchenko ; Wei Hu ;
> dev@dpdk.org
> Subject: Re: [EXTERNAL] Re: [PATCH 4/4] net/netvsc: cache device parameters
> for hot plug events
>
> On Wed, 29 Jan 2
On 03/02/2025 16:38, Nicholas Pratte wrote:
--- a/dts/tests/TestSuite_mtu.py
+++ b/dts/tests/TestSuite_mtu.py
@@ -164,22 +164,33 @@ def test_runtime_mtu_updating_and_forwarding(self) ->
None:
# Configure the new MTU.
# Start packet capturing.
-testpmd.
Forwarding restarts in the run-time MTU adjustment test case have been
explicitly added, given that the 'requires_forwarding_restart' decorator
from a previous patch was removed.
Signed-off-by: Nicholas Pratte
---
dts/tests/TestSuite_mtu.py | 13 -
1 file changed, 12 insertions(+), 1
This implementation conflicts with other bug fixes implemented in
earlier patches. The decorator was devised as a mean to make suite
writing a bit simpler, semantically, but the addition of this adds too
many complications for it to be worth implementing.
Signed-off-by: Nicholas Pratte
---
dts/f
v(2):
* Reworked the organzation of testpmd start and stop commands in
run-time MTU update and forwarding test.
While I initially thought that this would improve the cleanliness of
future test suite writing, because of the various nuances of each
testpmd run-time command, having the framewor
>
> The start and stop could be grouped by forwarding sections:
>
>set_mtu()
>
>start()
>assess()
>assess()
>stop()
>
>set_mtu()
>...
Alright, I'll fix that real quick!
On Mon, Feb 3, 2025 at 5:06 AM Andre Muezerie
wrote:
>
> As per guidance technical board meeting 2024/04/17. This series
> removes the use of VLAs from code built for Windows for all 3
> toolchains. If there are additional opportunities to convert VLAs
> to regular C arrays please provide the deta
Enforce separation of concerns by letting test runs being isolated
through a new TestRun class and respective module. This also means that
any actions taken on the nodes must be handled exclusively by the test
run. An example being the creation and destruction of the traffic
generator. TestSuiteWit
Add a new context module which holds the runtime context. The new
context will describe the current scenario and aid underlying classes
used by the test suites to automatically infer their parameters. This
futher simplies the test writing process as the test writer won't need
to be concerned about
Add a new module which defines the global runtime status of DTS and the
distinct execution stages and steps.
Signed-off-by: Luca Vizzarro
---
doc/api/dts/framework.status.rst | 8
doc/api/dts/index.rst| 1 +
dts/framework/logger.py | 36 --
dts/framewo
Make Port models standalone, so that they can be directly manipulated by
the test suites as needed. Moreover, let them handle themselves and
retrieve the logical name and mac address in autonomy.
Signed-off-by: Luca Vizzarro
---
dts/framework/testbed_model/linux_session.py | 47 +---
Change the Topology model to add further flexility in its usage as a
standalone entry point to test suites.
Signed-off-by: Luca Vizzarro
---
dts/framework/testbed_model/topology.py | 85 +
1 file changed, 45 insertions(+), 40 deletions(-)
diff --git a/dts/framework/testb
In an effort to improve separation of concerns, make the TestRunConfig
class responsible for processing the configured test suites. Moreover,
give TestSuiteConfig a facility to yield references to the selected test
cases.
Signed-off-by: Luca Vizzarro
---
dts/framework/config/__init__.py | 84 +++
The current configuration makes the user re-specify the port links for
each port in an unintuitive and repetitive way. Moreover, this design
does not give the user to opportunity to map the port topology as
desired.
This change adds a port_topology field in the test runs, so that the
user can use
Hi there,
This series enables the topology configuration and implements it in the
framework. Moreover, it performs quite a few refactors and a change on
how the test suites operate through the use of a Context. Finally, the
runtime internals are now isolated under the new TestRun and are further
r
https://bugs.dpdk.org/show_bug.cgi?id=1600
Luca Vizzarro (luca.vizza...@arm.com) changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Rather than having some of the idpf code split out into the "common"
directory, used by both a net/idpf and a net/cpfl driver, we can merge all idpf
code together under net/idpf and have the cpfl driver depend on "net/idpf"
rather than "common/idpf".
Signed-off-by: Bruce Richardson
---
devtool
The idpf driver was being built with warnings disabled for unused variables.
However, while the warning was being disabled in the base code directory, all
suppressed warnings were in the main directory.
Therefore, just remove the unused variables and re-enable the warnings.
Signed-off-by: Bruc
Hello Anatoly,
On Fri, Jan 31, 2025 at 1:59 PM Anatoly Burakov
wrote:
>
> Intel IGC and E1000 drivers are distinct, but they are actually generated
> from the same base code. This patchset will merge together all e1000-derived
> drivers into one common base, with three different ethdev driver
> f
25 matches
Mail list logo
