linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Haren Myneni <haren@linux.vnet.ibm.com>,
	herbert@gondor.apana.org.au, ddstreet@ieee.org,
	mikey@neuling.org, suka@us.ibm.com, npiggin@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org
Subject: Re: [1/2] crypto/nx: Use percpu send window for NX requests
Date: Tue, 14 Nov 2017 22:12:03 +1100 (AEDT)	[thread overview]
Message-ID: <3yblFv25bsz9sPr@ozlabs.org> (raw)
In-Reply-To: <1506321782.13257.4.camel@hbabu-laptop>

On Mon, 2017-09-25 at 06:43:02 UTC, Haren Myneni wrote:
> [PATCH 1/2] crypto/nx: Use percpu send window for NX requests
> 
> For P9 NX, the send window is opened for each crypto session and closed
> upon free. But VAS supports 64K windows per chip for all coprocessors
> including in user space support. So there is a possibility of not
> getting the window for kernel requests.
> 
> This patch reserves windows for each coprocessor type (NX842) and are
> available forever for kernel requests, Opens each window for each CPU
> on the corresponding chip during driver initialization. So then use the
> percpu txwin for NX requests depends on the CPU on which the process
> is executing.
> 
> Signed-off-by: Haren Myneni <haren@us.ibm.com>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/976dd6490b1b45727733a3ee1e25e1

cheers

      reply	other threads:[~2017-11-14 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  6:43 [PATCH 1/2] crypto/nx: Use percpu send window for NX requests Haren Myneni
2017-11-14 11:12 ` Michael Ellerman [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=3yblFv25bsz9sPr@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=ddstreet@ieee.org \
    --cc=haren@linux.vnet.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=npiggin@gmail.com \
    --cc=suka@us.ibm.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;
as well as URLs for NNTP newsgroup(s).