All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shally Verma <shallyv@marvell.com>
To: Fiona Trahe <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"paul.e.luse@intel.com" <paul.e.luse@intel.com>
Subject: Re: [PATCH v2] compressdev: add feature flag to specify	where processing is done
Date: Wed, 20 Feb 2019 16:00:43 +0000	[thread overview]
Message-ID: <BN6PR1801MB20526AA50481B376C85E7A76AD7D0@BN6PR1801MB2052.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1547746583-13832-1-git-send-email-fiona.trahe@intel.com>



>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Fiona Trahe
>Sent: 17 January 2019 23:06
>To: dev@dpdk.org
>Cc: pablo.de.lara.guarch@intel.com; fiona.trahe@intel.com; akhil.goyal@nxp.com; paul.e.luse@intel.com
>Subject: [dpdk-dev] [PATCH v2] compressdev: add feature flag to specify where processing is done
>
>External Email
>
>A new device feature flag, RTE_COMPDEV_FF_OP_DONE_IN_DEQUEUE
>is added. A PMD should set this if the bulk of the
>processing is done during the dequeue. It should leave it
>cleared if the bulk of the processing is done during the
>enqueue (default).
>Applications can use this as a hint for tuning.
>
>Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
Acked-by: Shally Verma <shally.verma@marvell.com>

Thanks
Shally

  reply	other threads:[~2019-02-20 16:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  1:39 [PATCH] compressdev: add feature flag to specify where processing is done 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
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 ` [PATCH v2] " Fiona Trahe
2019-02-20 16:00   ` Shally Verma [this message]
2019-03-22 15:09     ` 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=BN6PR1801MB20526AA50481B376C85E7A76AD7D0@BN6PR1801MB2052.namprd18.prod.outlook.com \
    --to=shallyv@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=paul.e.luse@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.