DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Mahipal Challa <mchalla@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	Ashish Gupta <ashishg@marvell.com>,
	Mahipal Challa <mchalla@marvell.com>
Subject: RE: [EXT] [dpdk-dev] [PATCH v1 1/1] compress/octeontx: scatter gather mode feature support
Date: Wed, 1 Feb 2023 14:27:17 +0000	[thread overview]
Message-ID: <CO6PR18MB4484A3B34BBC991C3C8D88C3D8D19@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230112075926.2864279-1-mchalla@marvell.com>

> Subject: [EXT] [dpdk-dev] [PATCH v1 1/1] compress/octeontx: scatter gather
> mode feature support

Rename title to 
compress/octeontx: support scatter gather mode

Fix checkpatch warning.
Add documentation update in .ini file.

> Scatter gather mode feature support is added to compress or decompress
> the larger data in a single compression or decompression operation.
> 
> Signed-off-by: Mahipal Challa <mchalla@marvell.com>
> ---
>  drivers/compress/octeontx/otx_zip.h     | 155 +++++++++++++++++++++---
>  drivers/compress/octeontx/otx_zip_pmd.c |  72 +++++++++--
>  2 files changed, 200 insertions(+), 27 deletions(-)
> 



> +#ifdef ZIP_DBG
> +		ZIP_PMD_INFO("ZIP SGL buf[%d], len = %d, iova =
> 0x%"PRIx64"\n",
> +			     sgidx, sginfo[sgidx].sg_ctl.s.length,
> +			     sginfo[sgidx].sg_addr.s.addr);
> +#endif
Can we use PMD debug logs instead of polluting the code with ZIP_DBG
If it is in datapath, we can define datapath macros which are compiled off by default.

      reply	other threads:[~2023-02-01 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  7:59 Mahipal Challa
2023-02-01 14:27 ` Akhil Goyal [this message]

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=CO6PR18MB4484A3B34BBC991C3C8D88C3D8D19@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ashishg@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mchalla@marvell.com \
    --cc=pathreya@marvell.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).