Re: [PATCH] net/mlx5: add queue hardware object context dump

[Raslan Darawsheh]

Hi,
From: Kiran Vedere 
Sent: Wednesday, June 5, 2024 12:11 AM
To: dev@dpdk.org
Cc: Matan Azrad; Raslan Darawsheh; Slava Ovsiienko; Dariusz Sosnowski
Subject: [PATCH] net/mlx5: add queue hardware object context dump

Add debug capability to mlx5 PMD to dump SQ/RQ/CQ HW object context for
a given port/queue. The context dump can provide some real-time
information on cause of certain Tx/Rx Failures.

Signed-off-by: Kiran Vedere 


Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

Re: [PATCH v3 0/8] net/mlx5: flow fast path validation

[Raslan Darawsheh]

Hi,
From: Dariusz Sosnowski 
Sent: Wednesday, June 26, 2024 9:14 PM
To: Slava Ovsiienko; Bing Zhao; Ori Kam; Suanming Mou; Matan Azrad
Cc: dev@dpdk.org
Subject: [PATCH v3 0/8] net/mlx5: flow fast path validation

This patchset adds validations for flow items and actions
supplied by the user to fast path async flow API functions
implemented in mlx5 PMD.

- Patches 1-7: Prepares mlx5 PMD for adding fast path validations.
  Specifically:

  - Required functionality for validating queue indexes and
target represented ports are extracted for reuse.
  - Additional info, required for validation, is stored in
pattern and actions templates.
  - Introduces mlx5_fp_debug_enabled() function for checking
if mlx5 PMD was compiled in debug mode.

- Patch 8: Introduce validations to:

  - rte_flow_async_create()
  - rte_flow_async_create_by_index()
  - rte_flow_async_actions_update()
  - rte_flow_async_destroy()

  These validations are enabled if and only if
  RTE_LIBRTE_MLX5_DEBUG macro is defined during compilation.

v3:
- Rebased on 24.07-rc1.
- Removed Depends-on tag for already marged ethdev patch.

v2:
- Split series 32095 into separate ethdev and mlx5 series.
- Rebased on latest commit in next-net-mlx-main.
- Removed Depends-on tags for already merged mlx5 patch series.

Dariusz Sosnowski (8):
  net/mlx5: extract target port validation
  net/mlx5: extract queue index validation
  net/mlx5: store pattern template items
  net/mlx5: store original actions in template
  net/mlx5: store expected type on indirect action
  net/mlx5: store modify field action
  common/mlx5: add debug mode indicator
  net/mlx5: add async flow operation validation

 doc/guides/rel_notes/release_24_07.rst |   1 +
 drivers/common/mlx5/mlx5_common.h  |  13 +
 drivers/net/mlx5/mlx5_flow.c   |  59 ++-
 drivers/net/mlx5/mlx5_flow.h   |  12 +
 drivers/net/mlx5/mlx5_flow_hw.c| 620 +++--
 5 files changed, 657 insertions(+), 48 deletions(-)

--
2.39.2


Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

[PATCH] net/netvsc: fix mtu_set in netvsc devices

[Alexander Skorichenko]

Prevent segfault in hn_reinit() caused by changing the MTU for
an incompletely initialized device.

Signed-off-by: Alexander Skorichenko 
---
 drivers/net/netvsc/hn_ethdev.c | 16 ++--
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/drivers/net/netvsc/hn_ethdev.c b/drivers/net/netvsc/hn_ethdev.c
index b8a32832d7..f8cb05a118 100644
--- a/drivers/net/netvsc/hn_ethdev.c
+++ b/drivers/net/netvsc/hn_ethdev.c
@@ -1127,8 +1127,10 @@ hn_reinit(struct rte_eth_dev *dev, uint16_t mtu)
int i, ret = 0;
 
/* Point primary queues at new primary channel */
-   rxqs[0]->chan = hv->channels[0];
-   txqs[0]->chan = hv->channels[0];
+   if (rxqs[0]) {
+   rxqs[0]->chan = hv->channels[0];
+   txqs[0]->chan = hv->channels[0];
+   }
 
ret = hn_attach(hv, mtu);
if (ret)
@@ -1140,10 +1142,12 @@ hn_reinit(struct rte_eth_dev *dev, uint16_t mtu)
return ret;
 
/* Point any additional queues at new subchannels */
-   for (i = 1; i < dev->data->nb_rx_queues; i++)
-   rxqs[i]->chan = hv->channels[i];
-   for (i = 1; i < dev->data->nb_tx_queues; i++)
-   txqs[i]->chan = hv->channels[i];
+   if (rxqs[0]) {
+   for (i = 1; i < dev->data->nb_rx_queues; i++)
+   rxqs[i]->chan = hv->channels[i];
+   for (i = 1; i < dev->data->nb_tx_queues; i++)
+   txqs[i]->chan = hv->channels[i];
+   }
 
return ret;
 }
-- 
2.34.1

[DPDK/ethdev Bug 1474] ptp

[bugzilla]

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

Bug ID: 1474
   Summary: ptp
   Product: DPDK
   Version: 23.07
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: Normal
 Component: ethdev
  Assignee: dev@dpdk.org
  Reporter: hendrik.huebne...@gmail.com
  Target Milestone: ---

Hello,

I seem to be having an issue with the DPDK ptpclient example.
The delta between master/slave clock hovers around -9000ns it very slowly keeps
going up a few ns at a time but not further than -8700ns.

Setup: 
I tested with two Intel E810 NICs. The ptp master is created with:

 sudo ptp4l -i enp24s0f0np0 -E -m -2

and the ice driver is bound to enp24s0f0np0.

The slave is created with sudo ./build/ptpclient -l 0 -n 4 -a 51:00.0 -- -T 0
-p 0x1

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

Re: [PATCH v2] net/memif: fix buffer overflow in zero copy Rx

[Patrick Robb]

I see this patchseries had a CI testing fail, for coremask DTS test on
Marvel CN10k. I don't think it could relate to the contents of your
patch though.

It had a timeout:

TestCoremask: Test Case test_individual_coremask Result FAILED:
TIMEOUT on ./arm64-native-linuxapp-gcc/app/test/dpdk-test  -c 0x8000
-n 2 --log-level="lib.eal,8"

So, I'm issuing a retest.
Recheck-request: iol-marvell-Functional

Re: Validation error in LDPC decoding

[Avijit Pandey]

Hello Nicolas,

Tagging you, as you helped in solving previous queries related to BBdev.

Any insights or guidance to help resolve this issue would be highly 
appreciated. If you need any more details, please feel free to ask.

Thank you for your time and assistance!



Best Regards,
Avijit Pandey
Cloud SME | VoerEir AB
+91 9598570190
[Title: LinkedIn - Description: image of LinkedIn 
icon]
   [Image]

From: Avijit Pandey 
Date: Wednesday, 26 June 2024 at 16:52
To: dev@dpdk.org 
Subject: Validation error in LDPC decoding
Hello Devs,

I hope this email finds you well.

I am reaching out to seek assistance regarding an issue I am facing in 
DPDK-BBdev utility, (v22.11).

I am performing some tests over a 5G Accelerator, ACC200 using DPDK-BBdev. I am 
creating custom test-vector files to generate custom load over the ACC200 
device. Currently, I am performing the LDPC decoding test through code block 
mode. I am creating the test-vector files with help of an open-source library, 
sionna (https://nvlabs.github.io/sionna/). Following are the steps to create 
input0 and output0 used in BBdev vector file. I have pulled out this code form 
the following reference: https://github.com/NVlabs/sionna/discussions/54.

k, n, q_m = 32, 64, 2
encoder = sn.fec.ldpc.LDPC5GEncoder(k, n, num_bits_per_symbol=q_m)
c = encoder(u)

e = c.numpy()

for i in range(e.shape[0]):
for j in flipped_positions[i]:
e[i][j] = 1.0 if e[i][j] == 0.0 else 0.0
e = tf.convert_to_tensor(e, np.float32)
decoder = sn.fec.ldpc.LDPC5GDecoder(encoder, hard_out=True, 
return_infobits=True, num_iter=20, cn_type="minsum")
w = decoder(2*e - 1)

When I use w as input0 and u as output0 in BBdev vector file I face following 
validation error:

Enqueue 32 reqs (phys 0x17ff8) to reg 0x118000
Debug : MMIO Enqueue
TestCase check_dec_status_and_ordering() line 1936 failed: op_status (8) != 
expected_status (0)
TestCase validate_ldpc_dec_op() line 2328 failed (err -1): Checking status and 
ordering for decoder failed
TestCase latency_test_ldpc_dec() line 4645 failed (err -1): Validation failed!
727:get_stats_from_queues() Got stats on 0
762:rte_bbdev_stats_get() Retrieved stats of device 0
602:rte_bbdev_stop() Stopped device 0
TestCase [ 0] : validation_tc failed
647:rte_bbdev_close() Closed device 0

Please find below the BBdev vector file created for the same

op_type =
RTE_BBDEV_OP_LDPC_DEC

input0=
0xff01ff01,0x0101ff01,0x0101ff01,0x01010101,0x0101ff01,0xff010101,0x01010101,0x01010101,0xff01ff01,0x0101ff01,0xff010101,0xff01,0xff0101ff,0x0101ff01,0x0101,0xff0101ff

output0=
0x

basegraph=
2

z_c=
8

q_m=
2

n_filler=
28

n_cb=
300

e=
64

rv_index =
0

code_block_mode =
1

iter_max =
20

expected_iter_count =
20

op_flags =
RTE_BBDEV_LDPC_ITERATION_STOP_ENABLE

expected_status =
OK

I would like to understand what incorrect configuration am I using?

Any insights or guidance to help resolve this issue would be highly 
appreciated. If you need any more details, please feel free to ask.

Thank you for your time and assistance!



Best Regards,
Avijit Pandey
Cloud SME | VoerEir AB
+91 9598570190
[Title: LinkedIn - Description: image of LinkedIn 
icon]
   [Image]