From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: why rte_power_ethdev_pmgmt_queue_enable need to check if other queues are stopped
Date: Mon, 20 Feb 2023 10:27:44 +0000 [thread overview]
Message-ID: <BN6PR11MB125181CC8523191BC53180F8F7A49@BN6PR11MB1251.namprd11.prod.outlook.com> (raw)
In-Reply-To: <0684cc0bac6f4b4996899b1dd9eafbf4@nokia-sbell.com>
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
Hi,
It is mainly because we’re install callbacks, which is not thread-safe unless the PMD is stopped. Our PMD’s internal config structures are not thread-safe. You should only start these ports after you configure everything.
From: Xiaoping Yan (NSB) <xiaoping.yan@nokia-sbell.com>
Sent: Monday, February 20, 2023 6:12 AM
To: users@dpdk.org; Burakov, Anatoly <anatoly.burakov@intel.com>
Subject: RE: why rte_power_ethdev_pmgmt_queue_enable need to check if other queues are stopped
Hi Anatoly
I see this multiple queue support is added by you.
Could you kindly help me to understand why rte_power_ethdev_pmgmt_queue_enable need other queues to be in stopped state?
commit 5dff9a72b0efeab02a2b71e52c4871805b7e64cb
Author: Anatoly Burakov anatoly.burakov@intel.com<mailto:anatoly.burakov@intel.com>
Date: Fri Jul 9 16:08:15 2021 +0000
power: support callbacks for multiple Rx queues
Thank you.
Br, Xiaoping
From: Xiaoping Yan (NSB)
Sent: 2023年2月16日 21:00
To: users@dpdk.org<mailto:users@dpdk.org>
Subject: why rte_power_ethdev_pmgmt_queue_enable need to check if other queues are stopped
Hi experts,
I’m trying to use dpdk power pmd management APIs in my dpdk application.
My application uses several ports, each have one rx queue, and it goes like this
1. Init first port, setup rx queue, call rte_power_ethdev_pmgmt_queue_enable, and start the first port
2. Init second port, setup rx queue, call rte_power_ethdev_pmgmt_queue_enable, and start the second port
3. …
Now for the first port & queue, rte_power_ethdev_pmgmt_queue_enable return success, but for the second port & queue, it returns -16
From rte_power_ethdev_pmgmt_queue_enable code, I think it fails when checking if other queues are stopped as well.
/* check if other queues are stopped as well */
ret = cfg_queues_stopped(lcore_cfg);
if (ret != 1) {
/* error means invalid queue, 0 means queue wasn't stopped */
ret = ret < 0 ? -EINVAL : -EBUSY;
goto end;
}
This seems quite strange for me, why other queues have to be in stopped state?
Can anyone help to explain?
Thank you.
Br, Xiaoping
[-- Attachment #2: Type: text/html, Size: 14434 bytes --]
next prev parent reply other threads:[~2023-02-20 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 12:59 Xiaoping Yan (NSB)
2023-02-20 6:12 ` Xiaoping Yan (NSB)
2023-02-20 10:27 ` Burakov, Anatoly [this message]
2023-02-20 13:40 ` Xiaoping Yan (NSB)
2023-02-20 13:59 ` Burakov, Anatoly
2023-02-20 14:10 ` Xiaoping Yan (NSB)
2023-02-20 14:19 ` Burakov, Anatoly
2023-02-21 1:00 ` Xiaoping Yan (NSB)
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=BN6PR11MB125181CC8523191BC53180F8F7A49@BN6PR11MB1251.namprd11.prod.outlook.com \
--to=anatoly.burakov@intel.com \
--cc=users@dpdk.org \
--cc=xiaoping.yan@nokia-sbell.com \
/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).