linux-kernel - Re: [PATCH RFC 1/2] crypto: Simple crypto algorithm load balancer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140118121145.GA19982@gondor.apana.org.au>
Date:	Sat, 18 Jan 2014 20:11:45 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Tadeusz Struk <tadeusz.struk@...el.com>
Cc:	linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
	davem@...emloft.net
Subject: Re: [PATCH RFC 1/2] crypto: Simple crypto algorithm load balancer

On Sat, Jan 18, 2014 at 12:46:08AM +0000, Tadeusz Struk wrote:
> Hi,
> In case of multiple crypto devices implementing the same algorithms
> the arbitration, which one to use is based on the cra_priority.
> Currently the algorithm with the highest priority is always be used.
> In case of two algorithms with the same priority the one added last is used.
> There is no load balancing and on a busy system there can be a situation when
> there more crypto accelerators, but only one is used for all crypto jobs
> and the others sit idle.
> This patch implements a simple load balancing based on the priority
> of an algorithm and its usage refctr. The distribution for 10 algorithms
> and 3000000 tfm_alloc allocations is as follows:

Have you looked at pcrypt and whether it can be extended to handle
this or perhaps something similar to pcrypt can be created?

Hard-coding this into the API seems a bit heavy-handed.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/