Hi Shally, > -----Original Message----- > From: Verma, Shally [mailto:shally.ve...@cavium.com] > Sent: Friday, February 2, 2018 11:27 AM > To: Trahe, Fiona <fiona.tr...@intel.com>; dev@dpdk.org > Cc: Gupta, Ashish <ashish.gu...@cavium.com>; Sahu, Sunila > <sunila.s...@cavium.com>; Challa, Mahipal <mahipal.cha...@cavium.com>; > Athreya, Narayana Prasad <narayanaprasad.athr...@cavium.com>; De Lara > Guarch, Pablo <pablo.de.lara.gua...@intel.com>; Jain, Deepak K > <deepak.k.j...@intel.com>; Roy Pledge <roy.ple...@nxp.com>; Youri > Querry <youri.querr...@nxp.com>; Hemant Agrawal > <hemant.agra...@nxp.com>; Ahmed Mansour > <ahmed.mans...@nxp.com>; De Lara Guarch, Pablo > <pablo.de.lara.gua...@intel.com> > Subject: RE: [RFC v3] Compression API in DPDK :SW ZLIB PMD ><deepak.k.j...@intel.com>; Roy Pledge <roy.ple...@nxp.com>; Youri > >Querry <youri.querr...@nxp.com>; Hemant Agrawal > ><hemant.agra...@nxp.com>; Ahmed Mansour > <ahmed.mans...@nxp.com>; De > >Lara Guarch, Pablo <pablo.de.lara.gua...@intel.com> > >Subject: RE: [RFC v3] Compression API in DPDK :SW ZLIB PMD > > > >Hi Fiona > > > >> I think a common draft repo would be the best way forward. Let's talk to > the maintainers about getting one set up. > >Sure. Please share us details when it is available. I assume it will be > >created > once API spec move from RFC to 1st version? > > > [Shally] Any update on this? We're available with sample SW ZLIB based > implementation (currently proof-concepted for stateless only) . So, if any > repo is available, we can upload it there.
We are working towards getting final internal approvals and will have more info. on this early next week. > > >Thanks > >Shally > > > >From: Trahe, Fiona [mailto:fiona.tr...@intel.com] > >Sent: 12 January 2018 00:31 > >To: Verma, Shally <shally.ve...@cavium.com>; dev@dpdk.org > >Cc: Gupta, Ashish <ashish.gu...@cavium.com>; Sahu, Sunila > ><sunila.s...@cavium.com>; Challa, Mahipal > <mahipal.cha...@cavium.com>; > >Athreya, Narayana Prasad <narayanaprasad.athr...@cavium.com>; De > Lara > >Guarch, Pablo <pablo.de.lara.gua...@intel.com>; Jain, Deepak K > ><deepak.k.j...@intel.com>; Roy Pledge <roy.ple...@nxp.com>; Youri > >Querry <youri.querr...@nxp.com>; Hemant Agrawal > ><hemant.agra...@nxp.com>; Ahmed Mansour > <ahmed.mans...@nxp.com>; Trahe, > >Fiona <fiona.tr...@intel.com>; De Lara Guarch, Pablo > ><pablo.de.lara.gua...@intel.com> > >Subject: RE: [RFC v3] Compression API in DPDK :SW ZLIB PMD > > > >Hi Shally, > > > > > >From: Verma, Shally [mailto:shally.ve...@cavium.com] > >Sent: Wednesday, January 10, 2018 8:33 AM > >To: Trahe, Fiona <mailto:fiona.tr...@intel.com>; mailto:dev@dpdk.org > >Cc: Gupta, Ashish <mailto:ashish.gu...@cavium.com>; Sahu, Sunila > ><mailto:sunila.s...@cavium.com>; Challa, Mahipal > ><mailto:mahipal.cha...@cavium.com>; Athreya, Narayana Prasad > ><mailto:narayanaprasad.athr...@cavium.com>; De Lara Guarch, Pablo > ><mailto:pablo.de.lara.gua...@intel.com>; Jain, Deepak K > ><mailto:deepak.k.j...@intel.com>; Roy Pledge > ><mailto:roy.ple...@nxp.com>; Youri Querry > ><mailto:youri.querr...@nxp.com>; Hemant Agrawal > ><mailto:hemant.agra...@nxp.com>; Ahmed Mansour > ><mailto:ahmed.mans...@nxp.com> > >Subject: [RFC v3] Compression API in DPDK :SW ZLIB PMD > > > >Hi Fiona > > > >We are planning to implement ZLIB based SW PMD to proof-concept DPDK > >compression RFC v3 API spec internally. However, would like to check If > >you're working upon similar in parallel and if yes, then what's your > >development roadmap / strategy so that we could see if we could leverage > joint effort. > >Depending upon your feedback, we can see if we can have some common > repo for joint development or send it as RFC patch. > > > >Let me know your opinion on same. > >[Fiona] We have not started a zlib based SW PMD, and would be delighted > >if you would do this, I agree it's a good way to prove out the API. > >We are writing some unit tests against the API, we would be happy to > >share these with you, and continue to develop these jointly so the same > test sets can be targeted against all PMDs. > >I think a common draft repo would be the best way forward. Let's talk to > the maintainers about getting one set up. > > > >Thanks > >Shally
