From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Ido Barnea (ibarnea)" <ibarnea@cisco.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "helin.zhang@intel.com" <helin.zhang@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: Put correct id values in ixgbevf_dev_xstats_get
Date: Thu, 9 Mar 2017 17:16:43 +0000 [thread overview]
Message-ID: <be4c3f2d-66ff-a0ad-132d-0066191a5a78@intel.com> (raw)
In-Reply-To: <ea28f1d9-d6b1-9df5-9c0f-9b4e49b66fae@intel.com>
On 3/9/2017 4:46 PM, Ferruh Yigit wrote:
> On 3/7/2017 2:28 PM, Ido Barnea (ibarnea) wrote:
>> Without setting the id, calling xstats_get twice with same array causes memory corruption.
>> Also, if IXGBEVF_NB_XSTATS will be different than 1 in the future, this will cause issues.
>>
>> Signed-off-by: Ido Barnea <ibarnea@cisco.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-09 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170307141824.69411-1-ibarnea@cisco.com>
2017-03-07 14:28 ` Ido Barnea (ibarnea)
2017-03-09 16:46 ` Ferruh Yigit
2017-03-09 17:16 ` Ferruh Yigit [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=be4c3f2d-66ff-a0ad-132d-0066191a5a78@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=ibarnea@cisco.com \
--cc=konstantin.ananyev@intel.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).