From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Shally Verma <shallyv@marvell.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Verma, Shally" <Shally.Verma@cavium.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
"Gupta, Ashish" <Ashish.Gupta@cavium.com>,
"Daly, Lee" <lee.daly@intel.com>,
"Luse, Paul E" <paul.e.luse@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done
Date: Wed, 16 Jan 2019 12:44:47 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896CB085@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <BN6PR1801MB20521CD810E6E773E40A98FCAD820@BN6PR1801MB2052.namprd18.prod.outlook.com>
Hi Shally,
> So, would like to understand it bit more on how flag would help app to tune itself as per current given
> description?
> For example, if PMD says, It does actual processing in dequeue, then how it will impact app design for
> better performance?
[Fiona] One example: It could enqueue a large burst, say 32 ops. Then if it tried to dequeue 32 ops that
could be a very long blocking call. So instead it could choose to dequeue 8 at a time.
Vice versa if work done in enqueue.
next prev parent reply other threads:[~2019-01-16 12:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 1:39 Fiona Trahe
2018-11-20 1:53 ` Stephen Hemminger
2018-11-20 16:25 ` Trahe, Fiona
2018-11-20 18:07 ` Stephen Hemminger
2018-12-18 14:43 ` Trahe, Fiona
2018-12-19 5:47 ` Verma, Shally
2018-12-19 17:09 ` Trahe, Fiona
2019-01-10 18:46 ` De Lara Guarch, Pablo
2019-01-12 6:47 ` Verma, Shally
2019-01-16 11:21 ` Shally Verma
2019-01-16 11:36 ` Trahe, Fiona
2019-01-16 12:09 ` Shally Verma
2019-01-16 12:44 ` Trahe, Fiona [this message]
2019-01-16 13:47 ` Shally Verma
2018-11-20 5:17 ` Verma, Shally
2018-11-20 16:40 ` Trahe, Fiona
2019-01-17 17:36 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2019-02-20 16:00 ` Shally Verma
2019-03-22 15:09 ` Akhil Goyal
2019-03-22 15:09 ` Akhil Goyal
2018-12-18 18:41 [dpdk-dev] [PATCH] " Luse, Paul E
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=348A99DA5F5B7549AA880327E580B435896CB085@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=Ashish.Gupta@cavium.com \
--cc=Shally.Verma@cavium.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ktejasree@marvell.com \
--cc=lee.daly@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=paul.e.luse@intel.com \
--cc=shallyv@marvell.com \
--cc=stephen@networkplumber.org \
--cc=tomaszx.jozwiak@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).