Re: Multiple paramters of input and output in DPDK-BBdev

["Avijit Pandey" <Avijit@voereir.com>]

[-- Attachment #1.1: Type: text/plain, Size: 4557 bytes --]

Hello Nicolas,

Thanks a lot for your support in resolving this query.


Best Regards,
Avijit Pandey
Cloud SME | VoerEir AB
+91 9598570190<tel:+917506391870>
[Title: LinkedIn - Description: image of LinkedIn icon]<https://www.linkedin.com/in/avijit-pandey-603206154/>
       [Image]

From: Chautru, Nicolas <nicolas.chautru@intel.com>
Date: Tuesday, 11 June 2024 at 03:57
To: Avijit Pandey <Avijit@voereir.com>, dev@dpdk.org <dev@dpdk.org>
Subject: RE: Multiple paramters of input and output in DPDK-BBdev
Hi,
Multiple input/output in test vector is not for multiple code blocks, but as an option for scatter-gather (data split into 2 pointers for instance for same code block, ie. not contiguous in memory). If you want to do 2 code blocks, these would be 2 independent operations and not what you are trying to do below.
Thanks,
Nic

From: Avijit Pandey <Avijit@voereir.com>
Sent: Thursday, June 6, 2024 3:33 AM
To: dev@dpdk.org
Cc: Chautru, Nicolas <nicolas.chautru@intel.com>
Subject: Multiple paramters of input and output in DPDK-BBdev

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 encoding test through code block mode. For the same, I have created a following vector file that includes multiple input and output parameters in following format:


      op_type=
      RTE_BBDEV_OP_LDPC_ENC

      input0=
      0x168356b5

      input1=
      0xb86ea705

      output0=
      0x77653168,0x49f8607b,0xb28dc29d,0xe52ce65c

      output1=
      0x0083eb76,0x20397a20,0x5927a0a5,0x6154eabe

      basegraph=
      2

      z_c=
      6

      q_m=
      1

      n_filler=
      28

      n_cb=
      300

      e=
      128

      rv_index =
      0

      code_block_mode =
      1

      op_flags =
      RTE_BBDEV_LDPC_RATE_MATCH

      expected_status =
      OK


When I execute the test through test-BBdev command:

      ./test-bbdev.py -e="-l 11 --vfio-vf-token=${UUID} --allow 0000:f7:00.2 --log-level lib.bbdev:debug" -l 4 -v /root/cb_mode_32_128_multi_data.data -c validation

I face the following error:

      == test: validation
      dev:0000:f7:00.2, burst size: 32, num ops: 32, op type: RTE_BBDEV_OP_LDPC_ENC
      TestCase validate_op_chain() line 1998 failed: Length of segment differ in original (16) and filled (0) op
      TestCase validate_enc_op() line 2385 failed (err -1): Output buffers (CB=0) are not equal
      TestCase latency_test_ldpc_enc() line 4748 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
       + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +
       + Test Suite Summary : BBdev Validation Tests
       + Tests Total :        1
       + Tests Skipped :      0
       + Tests Passed :       0
       + Tests Failed :       1
       + Tests Lasted :       99.2251 ms
       + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +



Here I would like understand if there is any wrong configuration that I am setting or if this flow of mulitple inputs and multiple outputs is unsupported?

Tagging @nicolas.chautru@intel.com<mailto:nicolas.chautru@intel.com>, as I see a lot of contribution from your end.

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 | VoerEirAB
+919598570190


[-- Attachment #1.2: Type: text/html, Size: 28473 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 1438 bytes --]

[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 8370 bytes --]