From: Kim Phillips <kim.phillips@freescale.com>
To: Vakul Garg <vakul@freescale.com>
Cc: <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>,
Shengzhou Liu <Shengzhou.Liu@freescale.com>,
Alex Porosanu <alexandru.porosanu@freescale.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: caam - set RDB bit in security configuration register
Date: Wed, 6 Feb 2013 19:33:15 -0600 [thread overview]
Message-ID: <20130206193315.cb27accf9a7a7f95870fb47f@freescale.com> (raw)
In-Reply-To: <1360151266-28428-1-git-send-email-vakul@freescale.com>
On Wed, 6 Feb 2013 17:17:46 +0530
Vakul Garg <vakul@freescale.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
next prev parent reply other threads:[~2013-02-07 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 11:47 Vakul Garg
2013-02-07 1:33 ` Kim Phillips [this message]
2013-02-07 4:38 ` Garg Vakul-B16394
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130206193315.cb27accf9a7a7f95870fb47f@freescale.com \
--to=kim.phillips@freescale.com \
--cc=Shengzhou.Liu@freescale.com \
--cc=alexandru.porosanu@freescale.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vakul@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®