From: Garg Vakul-B16394 <B16394@freescale.com>
To: Phillips Kim-R1AAHA <R1AAHA@freescale.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>,
Liu Shengzhou-B36685 <B36685@freescale.com>,
Porosanu Alexandru-B06830 <B06830@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] crypto: caam - set RDB bit in security configuration register
Date: Thu, 7 Feb 2013 04:38:46 +0000 [thread overview]
Message-ID: <065BBB7616BCE543832A2EF096986B9417E955@039-SN2MPN1-011.039d.mgd.msft.net> (raw)
In-Reply-To: <20130206193315.cb27accf9a7a7f95870fb47f@freescale.com>
> -----Original Message-----
> From: Phillips Kim-R1AAHA
> Sent: Thursday, February 07, 2013 7:03 AM
> To: Garg Vakul-B16394
> Cc: linux-crypto@vger.kernel.org; Herbert Xu; David S. Miller; Liu
> Shengzhou-B36685; Porosanu Alexandru-B06830; linux-kernel@vger.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@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
Ok
>
> > 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?
We measured USDPAA IPSEC throughput to be 1.9 times better on T4240 with this change.
>
> > + 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.
Ok
>
> Kim
prev parent reply other threads:[~2013-02-07 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 11:47 [PATCH] crypto: caam - set RDB bit in security configuration register Vakul Garg
2013-02-07 1:33 ` Kim Phillips
2013-02-07 4:38 ` Garg Vakul-B16394 [this message]
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=065BBB7616BCE543832A2EF096986B9417E955@039-SN2MPN1-011.039d.mgd.msft.net \
--to=b16394@freescale.com \
--cc=B06830@freescale.com \
--cc=B36685@freescale.com \
--cc=R1AAHA@freescale.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).