From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ori Kam <orika@mellanox.com>, matan@mellanox.com
Cc: dev@dpdk.org, dekelp@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the alloc size of rqt attribute
Date: Tue, 8 Oct 2019 13:33:02 +0100 [thread overview]
Message-ID: <140ce53c-30d8-66c5-f945-b08a4b467bd9@intel.com> (raw)
In-Reply-To: <1569493335-44790-1-git-send-email-orika@mellanox.com>
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?
next prev parent reply other threads:[~2019-10-08 12:33 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 [this message]
2019-10-10 8:36 ` 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=140ce53c-30d8-66c5-f945-b08a4b467bd9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--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).