From: Stephen Hemminger <stephen@networkplumber.org>
To: Fiona Trahe <fiona.trahe@intel.com>
Cc: dev@dpdk.org, akhil.goyal@nxp.com, tomaszx.jozwiak@intel.com,
shally.verma@caviumnetworks.com, ashish.gupta@caviumnetworks.com,
lee.daly@intel.com
Subject: Re: [PATCH] compressdev: add feature flag to specify where processing is done
Date: Mon, 19 Nov 2018 17:53:49 -0800 [thread overview]
Message-ID: <20181119175349.2bd2fdd1@xeon-e3> (raw)
In-Reply-To: <1542677988-3876-1-git-send-email-fiona.trahe@intel.com>
On Tue, 20 Nov 2018 01:39:48 +0000
Fiona Trahe <fiona.trahe@intel.com> wrote:
> A new device feature flag, RTE_COMPDEV_FF_SW_OP_DONE_IN_DEQUEUE
> is added. A PMD which processes operations using a software
> acceleration engine 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).
> An application may find this useful for tuning.
>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
What application? or is this "if we build it they will come?"
next prev parent reply other threads:[~2018-11-20 1:53 UTC|newest]
Thread overview: 20+ 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 [this message]
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
2019-03-22 15:09 ` Akhil Goyal
-- strict thread matches above, loose matches on Subject: below --
2018-12-18 18:41 [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=20181119175349.2bd2fdd1@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=akhil.goyal@nxp.com \
--cc=ashish.gupta@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=lee.daly@intel.com \
--cc=shally.verma@caviumnetworks.com \
--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 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.