From: Suanming Mou <suanmingm@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: Raslan Darawsheh <rasland@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix shared RSS action release
Date: Tue, 10 Nov 2020 01:44:44 +0000 [thread overview]
Message-ID: <MWHPR1201MB0189B664C0ABC8CE71AFB05EC1E90@MWHPR1201MB0189.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ae5fa422-7783-1a1b-abb6-157b58e76090@intel.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Tuesday, November 10, 2020 2:17 AM
> To: Suanming Mou <suanmingm@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Cc: Raslan Darawsheh <rasland@nvidia.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix shared RSS action release
>
> On 11/6/2020 3:08 AM, Suanming Mou wrote:
> > As shared RSS action is global standalone action, the shared action
> > should be maintained only by the shared action management functions.
> >
> > Currently, the shared RSS action hrxq uses the same fate action type
> > with existed general queues, and implicitly uses the deprecate refcnt
> > increment to indicate the hrxq is in using which leads the hrxq be
> > released when flow is destroyed.
> >
>
> Can you please re-word above paragraph to make it easier to understand?
OK, will send V2 with the update.
>
> Thanks,
> ferruh
>
> > This commit adds a new fate action type for shared RSS action to
> > handle the shared RSS action release correctly.
> >
> > Fixes: e1592b6c4dea ("net/mlx5: make Rx queue thread safe")
> >
> > Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> > Acked-by: Matan Azrad <matan@nvidia.com>
>
> <...>
next prev parent reply other threads:[~2020-11-10 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 3:08 Suanming Mou
2020-11-09 8:22 ` Raslan Darawsheh
2020-11-09 18:16 ` Ferruh Yigit
2020-11-10 1:44 ` Suanming Mou [this message]
2020-11-10 3:28 ` [dpdk-dev] [PATCH v2] " Suanming Mou
2020-11-11 12:39 ` Ferruh Yigit
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=MWHPR1201MB0189B664C0ABC8CE71AFB05EC1E90@MWHPR1201MB0189.namprd12.prod.outlook.com \
--to=suanmingm@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@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).