From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] app/compress-perf: prevent output buffer overflow
Date: Fri, 26 Jul 2019 12:55:20 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435897D1C1A@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190723095328.23236-1-adamx.dybkowski@intel.com>
> -----Original Message-----
> From: Dybkowski, AdamX
> Sent: Tuesday, July 23, 2019 10:53 AM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com
> Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Subject: [PATCH] app/compress-perf: prevent output buffer overflow
>
> This patch fixes the issue of memory overwrite after the end of
> the output buffer by calculating its size as the number of all
> segments multipled by the output segment size.
> Additionally buffer overflow errors returned by PMD driver are
> detected and shown, ending the test.
>
> Also the output buffer size multiplier was increased from 105%
> to 110% to allow running the tests on noncompressible files that
> expand to over 107% of original size during the compression.
>
> The changes were made in the verification part of the flow and
> they don't affect the benchmark results.
>
> Fixes: 424dd6c8c1 ("app/compress-perf: add weak functions for multicore test")
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2019-07-26 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 9:53 Adam Dybkowski
2019-07-26 12:55 ` Trahe, Fiona [this message]
2019-07-26 14:00 ` Akhil Goyal
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=348A99DA5F5B7549AA880327E580B435897D1C1A@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
/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).