From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Dave Jiang <dave.jiang@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, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v4 06/15] dmaengine: idxd: Add wq private data accessors
Date: Mon, 08 May 2023 15:55:55 -0500 [thread overview]
Message-ID: <5c2f8cd03b03627ca726ca2782887e501827ea7b.camel@linux.intel.com> (raw)
In-Reply-To: <2618f557-01a5-f76b-ad09-6eb0871cdf00@intel.com>
On Mon, 2023-05-08 at 13:43 -0700, Dave Jiang wrote:
>
>
> On 5/8/23 1:07 PM, Tom Zanussi wrote:
> > Add the accessors set_idxd_wq_private() and idxd_wq_private()
> > allowing
> > users to set and retrieve a private void * associated with an
> > idxd_wq.
> >
> > The private data is stored in the idxd_dev.conf_dev associated with
> > each idxd_wq.
> >
> > Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> > ---
> > drivers/dma/idxd/idxd.h | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/dma/idxd/idxd.h b/drivers/dma/idxd/idxd.h
> > index 193552dea224..71cd4ca7d27a 100644
> > --- a/drivers/dma/idxd/idxd.h
> > +++ b/drivers/dma/idxd/idxd.h
> > @@ -552,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)
>
> I would go with the same kernel naming convention:
>
> idxd_wq_set_private() and idxd_wq_get_private()?
Yeah, makes sense, will change.
Thanks,
Tom
> > +{
> > + dev_set_drvdata(wq_confdev(wq), private);
> > +}
> > +
> > +static inline void *idxd_wq_private(struct idxd_wq *wq)
> > +{
> > + return dev_get_drvdata(wq_confdev(wq));
> > +}
> > +
> > /*
> > * Intel IAA does not support batch processing.
> > * The max batch size of device, max batch size of wq and
next prev parent reply other threads:[~2023-05-08 20:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 20:07 [PATCH v4 00/15] crypto: Add Intel Analytics Accelerator (IAA) crypto compression driver Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 01/15] dmaengine: idxd: add wq driver name support for accel-config user tool Tom Zanussi
2023-05-09 17:48 ` Fenghua Yu
2023-05-09 18:17 ` Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 02/15] dmaengine: idxd: add external module driver support for dsa_bus_type Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 03/15] dmaengine: idxd: Export drv_enable/disable and related functions Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 04/15] dmaengine: idxd: Export descriptor management functions Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 05/15] dmaengine: idxd: Export wq resource " Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 06/15] dmaengine: idxd: Add wq private data accessors Tom Zanussi
2023-05-08 20:43 ` Dave Jiang
2023-05-08 20:55 ` Tom Zanussi [this message]
2023-05-08 20:07 ` [PATCH v4 07/15] dmaengine: idxd: add callback support for iaa crypto Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 08/15] crypto: iaa - Add IAA Compression Accelerator Documentation Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 09/15] crypto: iaa - Add Intel IAA Compression Accelerator crypto driver core Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 10/15] crypto: iaa - Add per-cpu workqueue table with rebalancing Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 11/15] crypto: iaa - Add compression mode management along with fixed mode Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 12/15] crypto: iaa - Add support for iaa_crypto deflate compression algorithm Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 13/15] crypto: iaa - Add support for default IAA 'canned' compression mode Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 14/15] crypto: iaa - Add irq support for the crypto async interface Tom Zanussi
2023-05-08 20:07 ` [PATCH v4 15/15] crypto: iaa - Add IAA Compression Accelerator stats 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=5c2f8cd03b03627ca726ca2782887e501827ea7b.camel@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=giovanni.cabiddu@intel.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=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