From: Bing Zhao <bingz@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the flow sync flags
Date: Fri, 30 Oct 2020 11:05:36 +0000 [thread overview]
Message-ID: <CY4PR1201MB0072DC2E75A96B7B265DFD39D0150@CY4PR1201MB0072.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ebd7ccd7-f6fd-3f12-85dd-cfc1a8c2b096@intel.com>
Thanks for your help, Ferruh.
BR. Bing
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Friday, October 30, 2020 6:10 PM
> To: Bing Zhao <bingz@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Ori Kam
> <orika@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the flow sync flags
>
> External email: Use caution opening links or attachments
>
>
> On 10/28/2020 12:23 PM, Bing Zhao wrote:
> > In order to synchronize the flow steering cache with hardware in
> DR
> > mode, the new function is introduced. The function needs to use
> both
> > flags of "MLX5DV_DR_DOMAIN_SYNC_FLAGS_SW/HW", or else some actions
> and
> > rules may get stuck in the work queue.
> >
> > And in some old OS release with inbox driver, the enum used in the
> > function is not introduced yet. To resolve this, a local defined
> macro
> > is introduced. Then in Verbs mode, it will still do nothing.
> > In DV mode, the glue layer will return the unsupport error.
> >
> > Fixes: 2e303780c17f ("net/mlx5: add flow sync API")
> >
> > Signed-off-by: Bing Zhao <bingz@nvidia.com>
> > Acked-by: Ori Kam <orika@nvidia.com>
> > Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2020-10-30 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 12:23 Bing Zhao
2020-10-30 10:10 ` Ferruh Yigit
2020-10-30 11:05 ` Bing Zhao [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=CY4PR1201MB0072DC2E75A96B7B265DFD39D0150@CY4PR1201MB0072.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=orika@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).