From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1303] [DPDK-23.11] hotplug_mp/attach_detach_dev_primary_cross_loop: re-attach device failed in multiple processes
Date: Fri, 20 Oct 2023 06:33:16 +0000 [thread overview]
Message-ID: <bug-1303-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3310 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1303
Bug ID: 1303
Summary: [DPDK-23.11]
hotplug_mp/attach_detach_dev_primary_cross_loop:
re-attach device failed in multiple processes
Product: DPDK
Version: 23.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: tingtingx.liao@intel.com
Target Milestone: ---
Environment
DPDK version: 77f913752a55c0262bfda99a1b69ca0bd804c6c7
OS: Ubuntu 22.04.3 LTS/5.15.0-82-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC hardware: Ethernet Controller E810-C for SFP 1593
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC driver: ice-1.13.0_rc90_2_g5c64af920_dirty
NIC firmware: 4.40 0x8001afdb 1.3444.0
Test Setup
1. compile hotplug_mp.
meson configure -Dexamples=multi_process/hotplug_mp x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
2. bind all PF to ice and start 3 processes
./usertools/dpdk-devbind.py -b ice 0000:18:00.0
PRIMARY process: x86_64-native-linuxapp-gcc/examples/dpdk-hotplug_mp
--proc-type=auto
SECONDARY process-1: x86_64-native-linuxapp-gcc/examples/dpdk-hotplug_mp
--proc-type=auto
SECONDARY process-2: x86_64-native-linuxapp-gcc/examples/dpdk-hotplug_mp
--proc-type=auto
3. bind all PF to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:18:00.0
4. attach device in PRIMARY process
attach 0000:18:00.0
5. detach device in SECONDARY process-1
detach 0000:18:00.0
6. re-attach device in PRIMARY process
attach 0000:18:00.0
[Output]
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_ice (8086:1593) device: 0000:18:00.0 (socket 1)
ice_load_pkg_type(): Active package is: 1.3.36.0, ICE OS Default Package
(double VLAN mode)
EAL: Failed to attach device on secondary process
EAL: Releasing PCI mapped resource for 0000:18:00.0
EAL: Calling pci_unmap_resource for 0000:18:00.0 at 0x2202010000
EAL: Calling pci_unmap_resource for 0000:18:00.0 at 0x2204010000
failed to attached device 0000:18:00.0
Expected Result
Explain what is the expected result in text or as an example output:
[Expected Result]
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_ice (8086:1593) device: 0000:18:00.0 (socket 1)
ice_load_pkg_type(): Active package is: 1.3.36.0, ICE OS Default Package
(double VLAN mode)
attached device 0000:18:00.0
Regression
Is this issue a regression: (Y/N)Y
commit 36c46e738120c381cf663c96692454c5aa75e203
Author: David Marchand <david.marchand@redhat.com>
Date: Wed Sep 27 13:45:15 2023 +0200
ethdev: cleanup shared data with the last port
If no port is allocated and no port owner is still registered,
ethdev from a primary process may release the memzone used to store
port data.
This makes it possible for the DPDK memory allocator to release
associated resources back to the OS.
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5389 bytes --]
reply other threads:[~2023-10-20 6:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1303-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).