From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 888] cannot close memif port
Date: Thu, 18 Nov 2021 17:22:15 +0000 [thread overview]
Message-ID: <bug-888-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=888
Bug ID: 888
Summary: cannot close memif port
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: sunnylandh@gmail.com
Target Milestone: ---
Created attachment 179
--> https://bugs.dpdk.org/attachment.cgi?id=179&action=edit
code to reproduce bug
I'm trying out DPDK 21.11-rc3 and noticed a regression.
If a port using net_memif driver has been started, it is not possible to close
the port.
This is because the rte_eth_dev_close function has a check that the port must
be stopped, but net_memif driver does not support dev_ops->dev_stop operation.
Consequently, it becomes impossible to stop and close the memif port.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-18 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 17:22 bugzilla [this message]
2021-11-26 18: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-888-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).