DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Suanming Mou <suanmingm@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	Matan Azrad <matan@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] net/mlx5: fix indexed pool bugs
Date: Mon, 20 Apr 2020 13:15:39 +0000	[thread overview]
Message-ID: <AM0PR05MB6707759300175EC1B7C4CDE8C2D40@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1587350076-58468-1-git-send-email-suanmingm@mellanox.com>

Hi,

> -----Original Message-----
> From: Suanming Mou <suanmingm@mellanox.com>
> Sent: Monday, April 20, 2020 5:35 AM
> To: Slava Ovsiienko <viacheslavo@mellanox.com>; Matan Azrad
> <matan@mellanox.com>
> Cc: Raslan Darawsheh <rasland@mellanox.com>; dev@dpdk.org
> Subject: [PATCH 0/2] net/mlx5: fix indexed pool bugs
> 
> These two patches fix the bugs with indexed memory pool.
> 
> 1. The incorrect pool entry size with mark reg copy.
> 2. The incorrect trunks free.
> 
> Suanming Mou (2):
>   net/mlx5: fix incorrect indexed pool configurations
>   net/mlx5: fix indexed pool incorrect trunks free
> 
>  drivers/net/mlx5/mlx5.c       | 4 ++--
>  drivers/net/mlx5/mlx5_utils.c | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> --
> 1.8.3.1


Patches squashed into relevant commits,
Applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2020-04-20 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  2:34 Suanming Mou
2020-04-20  2:34 ` [dpdk-dev] [PATCH 1/2] net/mlx5: fix incorrect indexed pool configurations Suanming Mou
2020-04-20  2:34 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix indexed pool incorrect trunks free Suanming Mou
2020-04-20 13:15 ` 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=AM0PR05MB6707759300175EC1B7C4CDE8C2D40@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=suanmingm@mellanox.com \
    --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).