From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Dan Streetman <ddstreet@ieee.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
mikey@neuling.org, suka@us.ibm.com, Ram Pai <linuxram@us.ibm.com>,
npiggin@gmail.com, Haren Myneni <hbabu@us.ibm.com>
Subject: Re: [PATCH V3 6/6] crypto/nx: Add P9 NX support for 842 compression engine
Date: Tue, 29 Aug 2017 18:02:09 -0700 [thread overview]
Message-ID: <59A60E91.8020803@linux.vnet.ibm.com> (raw)
In-Reply-To: <1504043837.2358.38.camel@kernel.crashing.org>
On 08/29/2017 02:57 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2017-08-29 at 14:54 -0700, Haren Myneni wrote:
>> Opening send window for each crypto transform (crypto_alloc,
>> compression/decompression, ..., crypto_free) so that does not have to
>> wait for the previous copy/paste complete. VAS will map send and
>> receive windows, and can cache in send windows (up to 128). So I
>> thought using the same send window (per chip) for more requests (say
>> 1000) may be adding overhead.
>>
>> I will make changes if you prefer using 1 send window per chip.
>
> Did you check the cost of opening/closing a window ?
No, Not yet. opening / closing happens only during alloc/free, but not for each compression/decompression. Hence used separate send windows.
Thanks
Haren
>
> Cheers,
> Ben.
>
next prev parent reply other threads:[~2017-08-30 1:02 UTC|newest]
Thread overview: 28+ 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
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 [this message]
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 13:42 ` Michael Neuling
2017-09-02 16:17 ` Dan Streetman
2017-09-02 16:17 ` Dan Streetman
2017-09-03 8:32 ` Haren Myneni
2017-09-03 14:12 ` Dan Streetman
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=59A60E91.8020803@linux.vnet.ibm.com \
--to=haren@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=ddstreet@ieee.org \
--cc=hbabu@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.