From: Christian Marangi <ansuelsmth@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Antoine Tenart <atenart@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
upstream@airoha.com, Richard van Schagen <vschagen@icloud.com>
Subject: Re: [PATCH v8 3/3] crypto: Add Inside Secure SafeXcel EIP-93 crypto engine support
Date: Sat, 14 Dec 2024 14:32:26 +0100 [thread overview]
Message-ID: <675d88f1.7b0a0220.325e04.7513@mx.google.com> (raw)
In-Reply-To: <Z10LgtZm4-qCB2aL@gondor.apana.org.au>
On Sat, Dec 14, 2024 at 12:37:22PM +0800, Herbert Xu wrote:
> On Wed, Dec 11, 2024 at 12:39:13PM +0100, Christian Marangi wrote:
> >
> > Do you have quick example for this?
>
> Just search for crypto_ahash_set_reqsize in drivers/crypto and see
> how they use the reqctx to store temporary data. For each request,
> you're guaranteed to have exclusive ownership of the reqctx.
>
> If you wish to DMA into the reqctx, search for ahash_request_ctx_dma
> to see how you should set it up.
>
Oh ok I didn't understood you were referring to the request_ctx API
thanks.
I just pushed v9 with the requested changes done. Now we map DMA only
when needed and use local struct instead of kmalloc. kmalloc is only
used for blocks. For that GFP_ATOMIC is used. The ALLOCATES_MEMORY was
already set in the algo flags.
Hope I'm making good progress on this.
--
Ansuel
next prev parent reply other threads:[~2024-12-14 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 20:48 [PATCH v8 0/3] crypto: Add EIP-93 crypto engine support Christian Marangi
2024-12-10 20:48 ` [PATCH v8 1/3] spinlock: extend guard with spinlock_bh variants Christian Marangi
2024-12-10 20:48 ` [PATCH v8 2/3] dt-bindings: crypto: Add Inside Secure SafeXcel EIP-93 crypto engine Christian Marangi
2024-12-10 20:48 ` [PATCH v8 3/3] crypto: Add Inside Secure SafeXcel EIP-93 crypto engine support Christian Marangi
2024-12-11 9:30 ` Herbert Xu
2024-12-11 11:39 ` Christian Marangi
2024-12-14 4:37 ` Herbert Xu
2024-12-14 13:32 ` Christian Marangi [this message]
2024-12-11 9:39 ` Herbert Xu
2024-12-11 11:40 ` Christian Marangi
2024-12-11 23:18 ` Herbert Xu
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=675d88f1.7b0a0220.325e04.7513@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=atenart@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=justinstitt@google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=upstream@airoha.com \
--cc=vschagen@icloud.com \
--cc=will@kernel.org \
/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