DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Ori Kam <orika@mellanox.com>, Matan Azrad <matan@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the alloc size of rqt attribute
Date: Thu, 10 Oct 2019 08:36:16 +0000	[thread overview]
Message-ID: <DB3PR0502MB3964F80844713D9AB72C91C6C2940@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <140ce53c-30d8-66c5-f945-b08a4b467bd9@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ferruh Yigit
> Sent: Tuesday, October 8, 2019 3:33 PM
> To: Ori Kam <orika@mellanox.com>; Matan Azrad <matan@mellanox.com>
> Cc: dev@dpdk.org; Dekel Peled <dekelp@mellanox.com>
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the alloc size of rqt attribute
> 
> On 9/26/2019 11:22 AM, Ori Kam wrote:
> > The receive queues list size is based on the size of uint32_t, so
> > when allocating the memory, the correct value should be used. Or
> > else there is risk to corrupt the memory, depending on the queues
> > number, because there is some pad area for alignment. If the queue
> > number is not large enough, the issue couldn't be observed.
> >
> > Based on Bing fix.
> >
> 
> Bing fix?

I've simply removed this from the commit log after having a talk to Ori since he is on vacation.
It's just something left which is not necessary

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2019-10-10  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 10:22 Ori Kam
2019-10-08  9:41 ` Slava Ovsiienko
2019-10-08 11:52 ` Raslan Darawsheh
2019-10-08 12:33 ` Ferruh Yigit
2019-10-10  8:36   ` 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=DB3PR0502MB3964F80844713D9AB72C91C6C2940@DB3PR0502MB3964.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=matan@mellanox.com \
    --cc=orika@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).