DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1268] dma/idxd appends extra characters which makes test-dma-perf to fail.
Date: Tue, 25 Jul 2023 14:54:49 +0000	[thread overview]
Message-ID: <bug-1268-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

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

            Bug ID: 1268
           Summary: dma/idxd appends extra characters which makes
                    test-dma-perf to fail.
           Product: DPDK
           Version: 23.07
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: vipin.varghese@amd.com
  Target Milestone: ---

Created attachment 256
  --> https://bugs.dpdk.org/attachment.cgi?id=256&action=edit
name change before-after

setup details:
1. CPU: Intel(R) Xeon(R) Gold 6421N
2. OS: Ubuntu 22.04.2 LTS
3. gcc: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1)
4. DPDk version: `https://git.dpdk.org/dpdk/tag/?id=v23.07-rc4`
5. DSA Acceleration: `f2:01.0 System peripheral: Intel Corporation Device 0b25`
6. application: `./build/app/dpdk-test-dma-perf`
7. arguments: `-l8-31 --log-level=pmd,8 -a 0000:f2:01.0 --config
app/test-dma-perf/my.ini`
8. driver used: vfio-pci on PF

INI config file:
```
[case1]
type=DMA_MEM_COPY
mem_size=10
buf_size=64,64,0,ADD
dma_ring_size=1024
kick_batch=32
src_numa_node=0
dst_numa_node=0
cache_flush=0
test_seconds=10
lcore_dma=lcore10@0000:f2:01.0
#lcore_dma=lcore10@0000:00:04.2, lcore11@0000:00:04.3
eal_args=--in-memory --file-prefix=test-dma-hw
```

issue logs:
```
Running scenario 1
Error: Fail to find DMA 0000:f2:01.0.
Not enough dmadevs (0) for all workers (1).
Stopping dmadev 0
dma: Device 0 already stopped.
No proper operation for variable entry.
```

reason for failure: the device name is populated from `idxd_pci.c` as
`0000:f2:01.0-q0`

actions tried:
1. modified by forcing `--proc-type=primary`. same issue 
2. modified name in ini `0000:f2:01.0-q0`, worked.

Checking the driver/dma/idxd_pci.c show cases the issue comes because the
application is identified as `RTE_SECONDARY`. attaching screen shot for the
same.

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

[-- Attachment #2: Type: text/html, Size: 4183 bytes --]

             reply	other threads:[~2023-07-25 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 14:54 bugzilla [this message]
2023-07-31 13:02 ` bugzilla

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=bug-1268-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).