From: Raslan Darawsheh <rasland@mellanox.com>
To: Matan Azrad <matan@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix DevX event registration timing
Date: Tue, 22 Oct 2019 13:30:04 +0000 [thread overview]
Message-ID: <DB3PR0502MB39646785CA623C45FB11D53FC2680@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1571729615-22925-1-git-send-email-matan@mellanox.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Matan Azrad
> Sent: Tuesday, October 22, 2019 10:34 AM
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@mellanox.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix DevX event registration timing
>
> The DevX counter management triggers an asynchronous event to get back
> the new counters values from the HW.
>
> The counter management doesn't trigger 2 parallel events for the same
> pool, hence, the pool cannot be updated again in the event waiting time.
>
> When the port is stopped, the DevX event mechanism wrongly was
> destroyed what remained all the waiting pools in waiting state forever.
>
> As a result, the counters of the stuck pools were never updated again.
>
> Separate the DevX interrupt installation from the dev installation and
> remove the DevX interrupt unregistration\registration from the
> stop\start operations.
>
> Now, the DevX interrupt should be installed in probe and uninstalled in
> close.
>
> Cc: stable@dpdk.org
> Fixes: f15db67df09c ("net/mlx5: accelerate DV flow counter query")
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Acked-by: Slava Ovsiienko <viacheslavo@mellanox.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2019-10-22 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 7:33 Matan Azrad
2019-10-22 13:30 ` Raslan Darawsheh [this message]
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=DB3PR0502MB39646785CA623C45FB11D53FC2680@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.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).