DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: why rte_power_ethdev_pmgmt_queue_enable need to check if other queues are stopped
Date: Thu, 16 Feb 2023 12:59:56 +0000	[thread overview]
Message-ID: <0c6664b4318142df94531165fb2acf94@nokia-sbell.com> (raw)

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

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: 9650 bytes --]

             reply	other threads:[~2023-02-16 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 12:59 Xiaoping Yan (NSB) [this message]
2023-02-20  6:12 ` Xiaoping Yan (NSB)
2023-02-20 10:27   ` Burakov, Anatoly
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=0c6664b4318142df94531165fb2acf94@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.com \
    --cc=users@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).