DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Ophir Munk <ophirmu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Matan Azrad" <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: Ophir Munk <ophirmu@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/mlx5: fix rxq object allocation with MPRQ
Date: Thu, 5 Nov 2020 10:05:51 +0000	[thread overview]
Message-ID: <DM6PR12MB274897A477B2A1935FFB9803CFEE0@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201104075520.23508-1-ophirmu@nvidia.com>


> -----Original Message-----
> From: Ophir Munk <ophirmu@nvidia.com>
> Sent: Wednesday, November 4, 2020 9:55 AM
> To: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Cc: Ophir Munk <ophirmu@nvidia.com>
> Subject: [PATCH v1] net/mlx5: fix rxq object allocation with MPRQ
> The space for extra buffer pointers used by MPRQ routines was not
> allocated in Rx queue object creation structure causing memory
> corruption.
> The fix allocates the extra memory for the pointers in case MPRQ is
> engaged.
> Fixes: f6dcff4788a1 ("net/mlx5: configure Rx queue for buffer split")
> Signed-off-by: Ophir Munk <ophirmu@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_rxq.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2020-11-05 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  7:55 Ophir Munk
2020-11-05 10:05 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR12MB274897A477B2A1935FFB9803CFEE0@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=ophirmu@nvidia.com \
    --cc=viacheslavo@nvidia.com \


* 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).