From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Xueming Li <xuemingl@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Matan Azrad <matan@mellanox.com>
Subject: RE: [PATCH] examples/vdpa: fix disabled VirtQ statistics query
Date: Thu, 3 Mar 2022 06:45:01 +0000 [thread overview]
Message-ID: <SN6PR11MB3504ED3B095A9E6F96040C3C9C049@SN6PR11MB3504.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220224132405.1939006-1-xuemingl@nvidia.com>
Hi Xueming,
> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, February 24, 2022 9:24 PM
> To: dev@dpdk.org
> Cc: xuemingl@nvidia.com; stable@dpdk.org; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Xia, Chenbo <chenbo.xia@intel.com>; Matan Azrad
> <matan@mellanox.com>
> Subject: [PATCH] examples/vdpa: fix disabled VirtQ statistics query
>
> Quit VirtQ statistics query instead of reporting error.
>
> Fixes: 6505865aa8ed ("examples/vdpa: add statistics show command")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> ---
> examples/vdpa/main.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/examples/vdpa/main.c b/examples/vdpa/main.c
> index 5ab07655aed..bd66deca85c 100644
> --- a/examples/vdpa/main.c
> +++ b/examples/vdpa/main.c
> @@ -391,7 +391,9 @@ static void cmd_device_stats_parsed(void *parsed_result,
> struct cmdline *cl,
> struct rte_vdpa_device *vdev = rte_vdpa_find_device_by_name(res->bdf);
> struct vdpa_port *vport = NULL;
> uint32_t first, last;
> + int vq_disabled = -1;
> int i;
> + int ret;
>
> if (!vdev) {
> RTE_LOG(ERR, VDPA, "Invalid device: %s.\n",
> @@ -449,8 +451,20 @@ static void cmd_device_stats_parsed(void *parsed_result,
> struct cmdline *cl,
> cmdline_printf(cl, "\nDevice %s:\n", res->bdf);
> for (; first <= last; first++) {
> memset(vport->stats, 0, sizeof(*vport->stats) * vport->stats_n);
> - if (rte_vdpa_get_stats(vport->dev, (int)first, vport->stats,
> - vport->stats_n) <= 0) {
> + ret = rte_vdpa_get_stats(vport->dev, (int)first, vport->stats,
> + vport->stats_n);
> + if (ret == 0) {
> + /* VQ disabled. */
> + if (vq_disabled == -1)
> + vq_disabled = (int)first;
> + continue;
I am not sure. Does ret == 0 mean VQ is disabled in this API? Because I don't see
anything special described in API doxygen about return value equals zero.
> + }
> + if (vq_disabled != -1) {
> + cmdline_printf(cl, "\tVirtq %d - %d disabled\n",
> + vq_disabled, (int)first - 1);
Let's check if vq_disabled == first - 1 to make different log. I will feel strange
if I see log like 'Virq 2-2 disabled'.
Thanks,
Chenbo
> + vq_disabled = -1;
> + }
> + if (ret < 0) {
> RTE_LOG(ERR, VDPA, "Failed to get vdpa queue statistics"
> " for device %s qid %d.\n", res->bdf,
> (int)first);
> @@ -464,6 +478,9 @@ static void cmd_device_stats_parsed(void *parsed_result,
> struct cmdline *cl,
> vport->stats[i].value);
> }
> }
> + if (vq_disabled != -1)
> + cmdline_printf(cl, "\tVirtq %d - %d disabled\n",
> + vq_disabled, (int)first - 1);
> }
>
> cmdline_parse_token_string_t cmd_device_stats_ =
> --
> 2.35.1
next prev parent reply other threads:[~2022-03-03 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:24 Xueming Li
2022-03-03 6:45 ` Xia, Chenbo [this message]
2022-04-22 8:40 ` Maxime Coquelin
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=SN6PR11MB3504ED3B095A9E6F96040C3C9C049@SN6PR11MB3504.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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).