linux-kernel - Re: [PATCH] crypto: caam - set RDB bit in security configuration register

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130206193315.cb27accf9a7a7f95870fb47f@freescale.com>
Date:	Wed, 6 Feb 2013 19:33:15 -0600
From:	Kim Phillips <kim.phillips@...escale.com>
To:	Vakul Garg <vakul@...escale.com>
CC:	<linux-crypto@...r.kernel.org>,
	Herbert Xu <herbert@...dor.hengli.com.au>,
	"David S. Miller" <davem@...emloft.net>,
	Shengzhou Liu <Shengzhou.Liu@...escale.com>,
	Alex Porosanu <alexandru.porosanu@...escale.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] crypto: caam - set RDB bit in security configuration
 register

On Wed, 6 Feb 2013 17:17:46 +0530
Vakul Garg <vakul@...escale.com> wrote:

> This change is required for post SEC-5.0 devices which have RNG4. Setting RDB

wrap your commit message text to 75 chars

> in security configuration register allows CAAM to use the "Random Data Buffer"
> to be filled by a single request. The Random Data Buffer is large enough for
> ten packets to get their IVs from a single request. If the Random Data Buffer
> is not enabled, then each IV causes a separate request, and RNG4 hardware
> cannot keep up resulting in lower IPSEC throughput.

Linux kernel IPSec or another IPSEC stack?  how much lower?

> +	if (of_device_is_compatible(nprop, "fsl,sec-v5.0"))
> +		setbits32(&topregs->ctrl.scfgr, SCFGR_RDBENABLE);
> +

this belongs further down - at the end of the RNG4 initialization
section.

Kim

--
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/