Hi Kevin,
> have to be created anyway.
> > Imagine encrypting a 20M block- this means runtime PM API is called
> > 20 * 1024 / 4 =~ 5000 times. The slow down in my opinion doesn't make it
> worth it.
> > What is your opinion about this?
>
> OK, I'm not terribly familiar with the crypto API, so I
er.kernel.org; linux-o...@vger.kernel.org; Mark A. Greer
>> Subject: Re: [PATCH] OMAP: AES: Don't idle/start AES device between Encrypt
>> operations
>>
>> Joel A Fernandes writes:
>>
>> > Calling runtime PM API for every block causes serious perf hit to
P: AES: Don't idle/start AES device between Encrypt
> operations
>
> Joel A Fernandes writes:
>
> > Calling runtime PM API for every block causes serious perf hit to
> > crypto operations that are done on a long buffer.
> > As crypto is performed on a page boun
Joel A Fernandes writes:
> Calling runtime PM API for every block causes serious perf hit to
> crypto operations that are done on a long buffer.
> As crypto is performed on a page boundary, encrypting large buffers can
> cause a series of crypto operations divided by page. The runtime PM API
> is
Calling runtime PM API for every block causes serious perf hit to
crypto operations that are done on a long buffer.
As crypto is performed on a page boundary, encrypting large buffers can
cause a series of crypto operations divided by page. The runtime PM API
is also called those many times.
We ca
