DMA Engine development
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	fenghua.yu@intel.com, vkoul@kernel.org
Cc: tony.luck@intel.com, wajdi.k.feghali@intel.com,
	james.guilford@intel.com, kanchana.p.sridhar@intel.com,
	giovanni.cabiddu@intel.com, hdanton@sina.com,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH v3 06/15] dmaengine: idxd: Add private_data to struct idxd_wq
Date: Mon, 1 May 2023 07:50:02 -0700	[thread overview]
Message-ID: <f15d37e6-a352-9f5b-2cb7-ef2d48b2c977@intel.com> (raw)
In-Reply-To: <20230428205539.113902-7-tom.zanussi@linux.intel.com>



On 4/28/23 1:55 PM, Tom Zanussi wrote:
> Add a void * to idxd_wqs for user-defined context data, along with
> accessors set_idxd_wq_private() and idxd_wq_private().
> 
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>

> ---
>   drivers/dma/idxd/idxd.h | 12 ++++++++++++
>   1 file changed, 12 insertions(+)
> 
> diff --git a/drivers/dma/idxd/idxd.h b/drivers/dma/idxd/idxd.h
> index 719f9f1662ad..0402f97d6ff8 100644
> --- a/drivers/dma/idxd/idxd.h
> +++ b/drivers/dma/idxd/idxd.h
> @@ -216,6 +216,8 @@ struct idxd_wq {
>   	u32 max_batch_size;
>   
>   	char driver_name[WQ_NAME_SIZE + 1];
> +
> +	void *private_data;
>   };
>   
>   struct idxd_engine {
> @@ -550,6 +552,16 @@ static inline int idxd_wq_refcount(struct idxd_wq *wq)
>   	return wq->client_count;
>   };
>   
> +static inline void set_idxd_wq_private(struct idxd_wq *wq, void *private)
> +{
> +	wq->private_data = private;
> +}
> +
> +static inline void *idxd_wq_private(struct idxd_wq *wq)
> +{
> +	return wq->private_data;
> +}
> +
>   /*
>    * Intel IAA does not support batch processing.
>    * The max batch size of device, max batch size of wq and

  reply	other threads:[~2023-05-01 14:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 20:55 [PATCH v3 00/15] crypto: Add Intel Analytics Accelerator (IAA) crypto compression driver Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 01/15] dmaengine: idxd: add wq driver name support for accel-config user tool Tom Zanussi
2023-04-29  0:14   ` Fenghua Yu
2023-05-01 14:01     ` Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 02/15] dmaengine: idxd: add external module driver support for dsa_bus_type Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 03/15] dmaengine: idxd: Export drv_enable/disable and related functions Tom Zanussi
2023-05-01 18:39   ` Fenghua Yu
2023-04-28 20:55 ` [PATCH v3 04/15] dmaengine: idxd: Export descriptor management functions Tom Zanussi
2023-05-01 14:49   ` Dave Jiang
2023-05-01 18:41   ` Fenghua Yu
2023-04-28 20:55 ` [PATCH v3 05/15] dmaengine: idxd: Export wq resource " Tom Zanussi
2023-05-01 18:41   ` Fenghua Yu
2023-04-28 20:55 ` [PATCH v3 06/15] dmaengine: idxd: Add private_data to struct idxd_wq Tom Zanussi
2023-05-01 14:50   ` Dave Jiang [this message]
2023-05-01 18:50   ` Fenghua Yu
2023-04-28 20:55 ` [PATCH v3 07/15] dmaengine: idxd: add callback support for iaa crypto Tom Zanussi
2023-05-01 20:48   ` Fenghua Yu
2023-04-28 20:55 ` [PATCH v3 08/15] crypto: iaa - Add IAA Compression Accelerator Documentation Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 09/15] crypto: iaa - Add Intel IAA Compression Accelerator crypto driver core Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 10/15] crypto: iaa - Add per-cpu workqueue table with rebalancing Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 11/15] crypto: iaa - Add compression mode management along with fixed mode Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 12/15] crypto: iaa - Add support for iaa_crypto deflate compression algorithm Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 13/15] crypto: iaa - Add support for default IAA 'canned' compression mode Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 14/15] crypto: iaa - Add irq support for the crypto async interface Tom Zanussi
2023-04-28 20:55 ` [PATCH v3 15/15] crypto: iaa - Add IAA Compression Accelerator stats Tom Zanussi
2023-04-28 21:00   ` Randy Dunlap
2023-04-28 21:06     ` Tom Zanussi

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=f15d37e6-a352-9f5b-2cb7-ef2d48b2c977@intel.com \
    --to=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=giovanni.cabiddu@intel.com \
    --cc=hdanton@sina.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.guilford@intel.com \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.zanussi@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=vkoul@kernel.org \
    --cc=wajdi.k.feghali@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