From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1270] drivers/dma/skeleton/ is not setting pthread affinity based on the lcore shared as arguments
Date: Wed, 02 Aug 2023 12:26:33 +0000 [thread overview]
Message-ID: <bug-1270-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 5894 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1270
Bug ID: 1270
Summary: drivers/dma/skeleton/ is not setting pthread affinity
based on the lcore shared as arguments
Product: DPDK
Version: 23.07
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: vipin.varghese@amd.com
Target Milestone: ---
Issue: when using dpdk skeleton DMA with lcore arguments, we expect the
Software DMA to be affinitized to the selected lcore. Currently this is not
working.
Example: `./buildgcc/app/dpdk-test-dma-perf --config app/test-dma-perf/my.ini
--log-level=pmd.dma,8`
Logs:
```
config file parsing...
config file parsing complete.
Running cases...
Running case 1
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 4
EAL: Detected static linkage of DPDK
EAL: Selected IOVA mode 'VA'
EAL: No free 2048 kB hugepages reported on node 0
EAL: No free 2048 kB hugepages reported on node 1
EAL: No free 2048 kB hugepages reported on node 2
EAL: No free 2048 kB hugepages reported on node 3
skeldma_parse_vdev_args(): Parse lcore_id = 20
skeldma_probe(): Create dma_skeleton dmadev with lcore-id 20
TELEMETRY: No legacy callbacks, legacy socket not created
Number of used lcores: 31.
Running scenario 1
Number of used dmadevs: 1.
Start testing....
lcore 3, DMA dma_skeleton, DMA Ring Size: 1024, Kick Batch Size: 32.
Average Cycles/op: 526, Buffer Size: 64 B, Buffer Number: 81920, Memory: 10.00
MB, Frequency: 3.840 Ghz.
```
Current Behavior: currently dma core is running on free available core.
Configuration:
```
[case1]
│·································································
type=DMA_MEM_COPY
│·································································
mem_size=10
│·································································
buf_size=64,8192,2,MUL
│·································································
dma_ring_size=1024
│·································································
kick_batch=32
│·································································
src_numa_node=0
│·································································
dst_numa_node=0
│·································································
cache_flush=0
│·································································
test_seconds=2
│·································································
lcore_dma=lcore3@dma_skeleton
│·································································
eal_args=--in-memory --vdev=dma_skeleton,lcore=20 --no-pci -l1-31
```
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 7797 bytes --]
next reply other threads:[~2023-08-02 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 12:26 bugzilla [this message]
2023-10-20 6:39 ` 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-1270-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).