From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trybula, ArturX" <arturx.trybula@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] app/compress-perf: add external mbufs option
Date: Tue, 24 Sep 2019 12:52:53 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435898233E1@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190903094312.8780-3-adamx.dybkowski@intel.com>
> -----Original Message-----
> From: Dybkowski, AdamX
> Sent: Tuesday, September 3, 2019 10:43 AM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Trybula, ArturX <arturx.trybula@intel.com>
> Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Subject: [PATCH 2/2] app/compress-perf: add external mbufs option
>
> This patch adds new performance measurement option --external-mbufs
> that allocates and uses memzones as external buffers instead of
> putting the data directly inside mbufs.
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2019-09-24 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 9:43 [dpdk-dev] [PATCH 0/2] Add " Adam Dybkowski
2019-09-03 9:43 ` [dpdk-dev] [PATCH 1/2] test/compress: add external buffer in mbuf API test Adam Dybkowski
2019-09-24 13:05 ` Trahe, Fiona
2019-09-03 9:43 ` [dpdk-dev] [PATCH 2/2] app/compress-perf: add external mbufs option Adam Dybkowski
2019-09-24 12:52 ` Trahe, Fiona [this message]
2019-09-24 14:10 ` [dpdk-dev] [PATCH v2 0/2] Add " Adam Dybkowski
2019-09-24 14:10 ` [dpdk-dev] [PATCH v2 1/2] test/compress: add external buffer in mbuf API test Adam Dybkowski
2019-09-24 14:10 ` [dpdk-dev] [PATCH v2 2/2] app/compress-perf: add external mbufs option Adam Dybkowski
2019-09-24 16:47 ` [dpdk-dev] [PATCH v2 0/2] Add " Trahe, Fiona
2019-09-27 14:50 ` 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=348A99DA5F5B7549AA880327E580B435898233E1@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=arturx.trybula@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).