linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Haren Myneni <haren@linux.vnet.ibm.com>
Cc: mpe@ellerman.id.au, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	mikey@neuling.org, benh@kernel.crashing.org, suka@us.ibm.com,
	ddstreet@ieee.org, npiggin@gmail.com, hbabu@us.ibm.com
Subject: Re: [PATCH V3 6/6] crypto/nx: Add P9 NX support for 842 compression engine
Date: Mon, 24 Jul 2017 09:46:50 -0700	[thread overview]
Message-ID: <20170724164650.GA5628@ram.oc3035372033.ibm.com> (raw)
In-Reply-To: <1500699702.23205.8.camel@hbabu-laptop>

On Fri, Jul 21, 2017 at 10:01:42PM -0700, Haren Myneni wrote:
> 
> This patch adds P9 NX support for 842 compression engine. Virtual
> Accelerator Switchboard (VAS) is used to access 842 engine on P9.
> 
> For each NX engine per chip, setup receive window using
> vas_rx_win_open() which configures RxFIFo with FIFO address, lpid,
> pid and tid values. This unique (lpid, pid, tid) combination will
> be used to identify the target engine.
> 
> For crypto open request, open send window on the NX engine for
> the corresponding chip / cpu where the open request is executed.
> This send window will be closed upon crypto close request.
> 
> NX provides high and normal priority FIFOs. For compression /
> decompression requests, we use only hight priority FIFOs in kernel.
> 
> Each NX request will be communicated to VAS using copy/paste
> instructions with vas_copy_crb() / vas_paste_crb() functions.
> 

Reviewed-by: Ram Pai <linuxram@us.ibm.com>

> Signed-off-by: Haren Myneni <haren@us.ibm.com>
> ---
>  drivers/crypto/nx/Kconfig          |   1 +
>  drivers/crypto/nx/nx-842-powernv.c | 375 ++++++++++++++++++++++++++++++++++++-
>  drivers/crypto/nx/nx-842.c         |   2 +-
>  3 files changed, 371 insertions(+), 7 deletions(-)

  reply	other threads:[~2017-07-24 16:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22  5:01 [PATCH V3 6/6] crypto/nx: Add P9 NX support for 842 compression engine Haren Myneni
2017-07-24 16:46 ` Ram Pai [this message]
2017-08-28 23:25 ` Michael Ellerman
2017-08-29 13:32   ` Dan Streetman
2017-08-31  7:44     ` Haren Myneni
2017-08-31 13:40       ` Dan Streetman
2017-08-31 19:03         ` Haren Myneni
2017-09-01 11:34       ` Michael Ellerman
2017-09-02  4:11         ` Haren Myneni
2017-08-29  6:30 ` Sukadev Bhattiprolu
2017-08-29 13:58 ` Dan Streetman
2017-08-29 21:23   ` Benjamin Herrenschmidt
2017-08-29 21:54     ` Haren Myneni
2017-08-29 21:57       ` Benjamin Herrenschmidt
2017-08-30  1:02         ` Haren Myneni
2017-08-31 13:31       ` Dan Streetman
2017-08-31 19:09         ` Haren Myneni
2017-09-01 11:29         ` Michael Ellerman
2017-09-02  3:27           ` Haren Myneni
2017-09-02 16:14           ` Dan Streetman
2017-09-02  8:40   ` Haren Myneni
2017-09-02 13:42     ` Michael Neuling
2017-09-02 16:17     ` Dan Streetman
2017-09-03  8:32       ` Haren Myneni
2017-09-03 14:12         ` Dan Streetman

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=20170724164650.GA5628@ram.oc3035372033.ibm.com \
    --to=linuxram@us.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=ddstreet@ieee.org \
    --cc=haren@linux.vnet.ibm.com \
    --cc=hbabu@us.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=mpe@ellerman.id.au \
    --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).