DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dooley, Brian" <brian.dooley@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
	"Power, Ciara" <ciara.power@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH v5 1/3] common/qat: isolate parser arguments configuration
Date: Fri, 1 Mar 2024 16:07:56 +0000	[thread overview]
Message-ID: <SJ0PR11MB5056AA62575CF34817E65145835E2@SJ0PR11MB5056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240301155251.5101-1-arkadiuszx.kusztal@intel.com>

Hi Arek,

> -----Original Message-----
> From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> Sent: Friday, March 1, 2024 3:53 PM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Power, Ciara <ciara.power@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v5 1/3] common/qat: isolate parser arguments configuration
> 
> This commit isolates qat device arguments from the common code. Now
> arguments are defined per service, and only appear in the application if the
> service is compiled-in.
> 
> Depends-on: patch-137678 ("common/qat: add virtual qat device (vQAT)")
> 
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> v2:
> - added pmd isolation
> v3:
> - added fix for legacy flag
> v4:
> - fixed an issue with devargs segfault
> v5:
> - rebased against the newest changes in the pmd
> 
>  drivers/common/qat/qat_common.c     |  11 +++
>  drivers/common/qat/qat_common.h     |   3 +
>  drivers/common/qat/qat_device.c     | 189 +++++++++++++++++++-----------
> ------
>  drivers/common/qat/qat_device.h     |  27 ++----
>  drivers/compress/qat/qat_comp_pmd.c |  31 ++++--
>  drivers/compress/qat/qat_comp_pmd.h |   3 +-
>  drivers/crypto/qat/qat_asym.c       |  38 +++++---
>  drivers/crypto/qat/qat_sym.c        |  49 ++++++----
>  8 files changed, 198 insertions(+), 153 deletions(-)
> 
<snip>

Acked-by: Brian Dooley <brian.dooley@intel.com>

  parent reply	other threads:[~2024-03-01 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v4-00020240229093007.32298-1-arkadiuszx.kusztal@intel.com>
2024-02-29 19:14 ` [PATCH v4 " Arkadiusz Kusztal
2024-02-29 19:14   ` [PATCH v4 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-02-29 19:14   ` [PATCH v4 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-02-29 19:19   ` [EXTERNAL] [PATCH v4 1/3] common/qat: isolate parser arguments configuration Akhil Goyal
2024-03-01 15:52   ` [PATCH v5 " Arkadiusz Kusztal
2024-03-01 15:52     ` [PATCH v5 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-03-01 16:08       ` Dooley, Brian
2024-03-01 15:52     ` [PATCH v5 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-03-01 16:08       ` Dooley, Brian
2024-03-04  7:10         ` Akhil Goyal
2024-03-01 16:07     ` Dooley, Brian [this message]
2024-03-04  7:08     ` [EXTERNAL] [PATCH v5 1/3] common/qat: isolate parser arguments configuration Akhil Goyal

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=SJ0PR11MB5056AA62575CF34817E65145835E2@SJ0PR11MB5056.namprd11.prod.outlook.com \
    --to=brian.dooley@intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@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).