DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Daly, Lee" <lee.daly@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/3] compress/isal: enable checksum support in	driver
Date: Mon, 17 Dec 2018 09:20:07 +0000	[thread overview]
Message-ID: <F5C6929789601049BEB7272E267355987D9186@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2DC5B7@BGSMSX101.gar.corp.intel.com>

Hi Vipin, thanks for the question.

> -----Original Message-----
> From: Varghese, Vipin
> Sent: Monday, December 17, 2018 8:20 AM
> To: Daly, Lee <lee.daly@intel.com>; akhil.goyal@nxp.com
> Cc: dev@dpdk.org; Daly, Lee <lee.daly@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v4 1/3] compress/isal: enable checksum
> support in driver
> 
> Hi Lee,
> 
> Apologies if the logic is already done for my query
> 
> snipped
> > +		/* Set private xform checksum */
> > +		switch (xform->compress.chksum) {
> > +		/* Raw deflate by default */
> Does the user have to choose RTE_COMP_CHECKSUM_NONE while creating
> compress/isal instance?

At the moment, yes the application must fill out the xform/instance. 
> 
> > +		case(RTE_COMP_CHECKSUM_NONE):
> > +			priv_xform->compress.chksum = IGZIP_DEFLATE;
> > +			break;
> > +		case(RTE_COMP_CHECKSUM_CRC32):
> > +			priv_xform->compress.chksum =
> IGZIP_GZIP_NO_HDR;
> > +			break;
> > +		case(RTE_COMP_CHECKSUM_ADLER32):
> > +			priv_xform->compress.chksum =
> IGZIP_ZLIB_NO_HDR;
> > +			break;
> > +		case(RTE_COMP_CHECKSUM_CRC32_ADLER32):
> > +			ISAL_PMD_LOG(ERR, "Combined CRC and ADLER
> > checksum not"
> > +					" supported\n");
> > +			return -ENOTSUP;
> > +		default:
> > +			ISAL_PMD_LOG(ERR, "Checksum type not
> > supported\n");
> > +			return -ENOTSUP;
> Do we not fall back to RTE_COMP_CHECKSUM_NONE if the configuration is
> wrong and report warning?
> 

Right now, the xform must be filled out correctly before compression can be executed. 
Perhaps we could do as you say and fall back to a default config if the non-essential params are incorrect.
> snipped

  reply	other threads:[~2018-12-17  9:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11544697752-156863-1-git-send-email-lee.daly@intel.com>
2018-12-14  9:59 ` Lee Daly
2018-12-14  9:59   ` [dpdk-dev] [PATCH v4 2/3] test/compress: add checksum tests Lee Daly
2018-12-14  9:59   ` [dpdk-dev] [PATCH v4 3/3] doc: update ISA-L guide to reflect checksum support Lee Daly
2018-12-17  8:19   ` [dpdk-dev] [PATCH v4 1/3] compress/isal: enable checksum support in driver Varghese, Vipin
2018-12-17  9:20     ` Daly, Lee [this message]
2018-12-17 12:33       ` Varghese, Vipin
2018-12-19 15:48   ` [dpdk-dev] [PATCH v5 " Lee Daly
2018-12-19 15:48     ` [dpdk-dev] [PATCH v5 2/3] test/compress: add checksum tests Lee Daly
2018-12-19 15:48     ` [dpdk-dev] [PATCH v5 3/3] doc: update ISA-L guide to reflect checksum support Lee Daly
2019-01-08 10:29     ` [dpdk-dev] [PATCH v6 1/2] test/compress: add checksum tests Lee Daly
2019-01-08 10:29       ` [dpdk-dev] [PATCH v6 2/2] compress/isal: enable checksum support in driver Lee Daly
2019-01-08 14:58       ` [dpdk-dev] [PATCH v6 1/2] test/compress: add checksum tests De Lara Guarch, Pablo
2019-01-08 16:20       ` [dpdk-dev] [PATCH v7 " Lee Daly
2019-01-08 16:20         ` [dpdk-dev] [PATCH v7 2/2] compress/isal: enable checksum support in driver Lee Daly
2019-01-08 17:19         ` [dpdk-dev] [PATCH v7 1/2] test/compress: add checksum tests De Lara Guarch, Pablo

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=F5C6929789601049BEB7272E267355987D9186@IRSMSX106.ger.corp.intel.com \
    --to=lee.daly@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=vipin.varghese@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).