DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Erez Shitrit <erezsh@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Alex Vesker <valex@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH] net/mlx5/hws: fix shared context to use local defaults
Date: Wed, 22 Mar 2023 12:26:56 +0000	[thread overview]
Message-ID: <BYAPR12MB30780F4E1A723566944DC8D2CF869@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230322101621.642765-2-erezsh@nvidia.com>

Hi Erez,

> -----Original Message-----
> From: Erez Shitrit <erezsh@nvidia.com>
> Sent: Wednesday, March 22, 2023 12:16 PM
> To: dev@dpdk.org
> Cc: Alex Vesker <valex@nvidia.com>; stable@dpdk.org; Matan Azrad
> <matan@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH] net/mlx5/hws: fix shared context to use local defaults
> 
> 
Can you describe the problem first?

> Fix default miss behavior for shared resources, the problem
> could happen in two cases:
> When the table created, the default miss should go to the alias ft
> that will direct it back to local context.
> 
What is expected and what is currently happening?
> When the rule is without specific hit address and we are in a shared
> RTC from here it should be redirected back to the local context.
> 

How does your fix address this issue?

> Fixes: ce946c7d3999 ("net/mlx5/hws: support ibv context shared with local
> one")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
> Reviewed-by: Alex Vesker <valex@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---

As a general comment, 
1- this patch is a V3 of the original series : http://patches.dpdk.org/project/dpdk/list/?series=27465
2- you should be sending it as a reply to v1 and set version numbers in general stating the diff in between the versions.
3- I see only v1 was sent as one series then you decided to send it as one patch at a time is there a reason for that?
4- I'd appreciate it if you can send a V4 that has these details so that it will be clear on what is changing.

Kindest regards,
Raslan Darawsheh

  reply	other threads:[~2023-03-22 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 10:16 [PATCH] net/mlx5/hws: fix bug in pattern creation Erez Shitrit
2023-03-22 10:16 ` [PATCH] net/mlx5/hws: fix shared context to use local defaults Erez Shitrit
2023-03-22 12:26   ` Raslan Darawsheh [this message]
2023-03-22 14:42   ` [PATCH v4] " Erez Shitrit
2023-03-23  7:20     ` Raslan Darawsheh
2023-03-22 10:16 ` [PATCH] net/mlx5/hws: fix saving of jumbo tag for deletion Erez Shitrit
2023-03-22 14:44   ` [PATCH v4] " Erez Shitrit
2023-03-23  7:20     ` Raslan Darawsheh
2023-03-22 10:16 ` [PATCH] net/mlx5/hws: add check for modify-header actions Erez Shitrit
2023-03-22 14:45   ` [PATCH v4] " Erez Shitrit
2023-03-23  7:21     ` Raslan Darawsheh
2023-03-22 14:41 ` [PATCH v4] net/mlx5/hws: fix bug in pattern creation Erez Shitrit
2023-03-23  7:19   ` Raslan Darawsheh

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=BYAPR12MB30780F4E1A723566944DC8D2CF869@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=erezsh@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=valex@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).