Re: [PATCH v2] crypto: run qcrypto_pbkdf2_count_iters in a new thread

2024-12-10 Thread Daniel P . Berrangé
On Tue, Dec 10, 2024 at 06:29:49PM +0100, Thomas Huth wrote: > On 05/09/2024 01.52, Tiago Pasqualini wrote: > > CPU time accounting in the kernel has been demonstrated to have a > > sawtooth pattern[1][2]. This can cause the getrusage system call to > > not be as accurate as we are expecting, which

Re: [PATCH v2] crypto: run qcrypto_pbkdf2_count_iters in a new thread

2024-12-10 Thread Thomas Huth
On 05/09/2024 01.52, Tiago Pasqualini wrote: CPU time accounting in the kernel has been demonstrated to have a sawtooth pattern[1][2]. This can cause the getrusage system call to not be as accurate as we are expecting, which can cause this calculation to stall. The kernel discussions shows that

Re: [PATCH v2] crypto: run qcrypto_pbkdf2_count_iters in a new thread

2024-09-05 Thread Daniel P . Berrangé
On Wed, Sep 04, 2024 at 08:52:30PM -0300, Tiago Pasqualini wrote: > CPU time accounting in the kernel has been demonstrated to have a > sawtooth pattern[1][2]. This can cause the getrusage system call to > not be as accurate as we are expecting, which can cause this calculation > to stall. > > The

[PATCH v2] crypto: run qcrypto_pbkdf2_count_iters in a new thread

2024-09-04 Thread Tiago Pasqualini
CPU time accounting in the kernel has been demonstrated to have a sawtooth pattern[1][2]. This can cause the getrusage system call to not be as accurate as we are expecting, which can cause this calculation to stall. The kernel discussions shows that this inaccuracy happens when CPU time gets big