From: "Verma, Shally" <Shally.Verma@cavium.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.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>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done
Date: Sat, 12 Jan 2019 06:47:29 +0000 [thread overview]
Message-ID: <SN6PR07MB5152119C23E70EED1D3A98C7F0860@SN6PR07MB5152.namprd07.prod.outlook.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D89780362752@irsmsx112.ger.corp.intel.com>
HI Pablo
Sorry for delay in response.
>-----Original Message-----
>From: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
>Sent: 11 January 2019 00:17
>To: Trahe, Fiona <fiona.trahe@intel.com>; Verma, Shally <Shally.Verma@cavium.com>; Stephen Hemminger
><stephen@networkplumber.org>
>Cc: dev@dpdk.org; 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>; Trahe, Fiona
><fiona.trahe@intel.com>
>Subject: RE: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done
>
....
>> > >> 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.
>> > [Shally] Am seeing some of our HW based PMD also leveraging this
>> > choice. So I would say to make it generic feature flag instead of SW specific.
>> [Fiona] I can do but would like to understand this better first.
>> My understanding of HW offload is that the enqueue is just packaging up
>> the op and sending to the HW.
>> And the dequeue is just collecting the result from the HW and passing back
>> to the op.
>> The work is done by the HW accelerator, in between those 2 API calls, not
>> using any CPU cycles.
>> So what would it mean for HW to set OP_DONE_IN_DEQUEUE?
>
>Any comments on this? I agree with Fiona that this flag makes sense on SW only,
>but it seems that you have another use case.
I am waiting for feedback on this internally. Will revert on this as I get more information.
Thanks
Shally
>
>Thanks,
>Pablo
>
>>
>> > Thanks
>> > Shally
next prev parent reply other threads:[~2019-01-12 6:47 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 [this message]
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 ` [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=SN6PR07MB5152119C23E70EED1D3A98C7F0860@SN6PR07MB5152.namprd07.prod.outlook.com \
--to=shally.verma@cavium.com \
--cc=Ashish.Gupta@cavium.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=lee.daly@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=paul.e.luse@intel.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).