Hi,
On 6/25/25 08:32, Eric Biggers wrote:
That was the synchronous throughput. However, submitting multiple requests
asynchronously (which again, fscrypt doesn't actually do) barely helps.
Apparently the STM32 crypto engine has only one hardware queue.
I already strongly suspected that these n
Hello,
On 6/11/25 22:58, Eric Biggers wrote:
To protect users from these buggy and seemingly unhelpful drivers that I
have no way of testing, let's make fscrypt not use them. Unfortunately
there is no direct support for doing so in the Crypto API, but we can
achieve something very close to it b
On 6/13/25 16:42, Eric Biggers wrote:
Honestly, the responses to this thread so far have made it even more clear that
this patch is the right decision.
The chaining system I previously presented is just an example intended
to demonstrate the value of hardware drivers in the context of ST pla
