From: "Luse, Paul E" <paul.e.luse@intel.com>
To: 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>,
"shally.verma@caviumnetworks.com"
<shally.verma@caviumnetworks.com>,
"ashish.gupta@caviumnetworks.com"
<ashish.gupta@caviumnetworks.com>,
"Daly, Lee" <lee.daly@intel.com>,
"Luse, Paul E" <paul.e.luse@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] mail to ack
Date: Tue, 18 Dec 2018 18:39:07 +0000 [thread overview]
Message-ID: <82C9F782B054C94B9FC04A331649C77AB8C569B9@FMSMSX126.amr.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435896A4EED@IRSMSX101.ger.corp.intel.com>
-----Original Message-----
From: Trahe, Fiona
Sent: Tuesday, December 18, 2018 7:43 AM
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org; akhil.goyal@nxp.com; Jozwiak, TomaszX <tomaszx.jozwiak@intel.com>; shally.verma@caviumnetworks.com; ashish.gupta@caviumnetworks.com; Daly, Lee <lee.daly@intel.com>; Luse, Paul E <paul.e.luse@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>
Subject: RE: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done
Hi Stephen
//snip//
> > > Subject: Re: [dpdk-dev] [PATCH] compressdev: add feature flag to
> > > specify where processing is done
> > >
> > > 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?"
> > [Fiona] Our storage team asked for this, so not quite.
> > Seems like it might by generically useful, so a bit of the latter
> > too :) Would you prefer I removed that line?
>
> Hopefully, there would be one or more open source projects using the API.
> I just did a survey of DPDK an 1/3 of it is never used by any open
> source project. Hate to see more dead code and special cases created.
>
> At least, some example code in examples would help. Something like a
> simple in memory compressed storage server using a network API
> (SMB?/SSH?/FTP?)
[Fiona] There is no compressdev sample app yet.
However I've double-checked with the SPDK team, they're currently integrating compressdev and intend to push a patch to SPDK - a storage open-source project - using this flag.
Acked-by: Paul Luse <paul.e.luse@intel.com>
parent reply other threads:[~2018-12-18 18:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <348A99DA5F5B7549AA880327E580B435896A4EED@IRSMSX101.ger.corp.intel.com>]
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=82C9F782B054C94B9FC04A331649C77AB8C569B9@FMSMSX126.amr.corp.intel.com \
--to=paul.e.luse@intel.com \
--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=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).