From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Nicholas Piggin <nicholas.piggin@gmail.com>,
mikey@neuling.org, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
ddstreet@ieee.org
Subject: Re: [PATCH V2 0/6] Enable NX 842 compression engine on Power9
Date: Tue, 18 Jul 2017 11:53:52 -0700 [thread overview]
Message-ID: <596E5940.7000207@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170718180600.GB21838@us.ibm.com>
On 07/18/2017 11:06 AM, Sukadev Bhattiprolu wrote:
> Nicholas Piggin [nicholas.piggin@gmail.com] wrote:
>> On Mon, 17 Jul 2017 16:43:19 -0700
>> Haren Myneni <haren@linux.vnet.ibm.com> wrote:
>>
>>> [PATCH V2 0/6] Enable NX 842 compression engine on Power9
>>> This patchset depends on VAS kernel changes:
>>> https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-May/158178.html
>>
>> Just a question, we no longer invalidate the copy buffer on context
>> switch after this patch:
>>
>> 07d2a628bc ("powerpc/64s: Avoid cpabort in context switch when possible")
>>
>> If your vas address mappings are visible only to kernel, only used in
>> process / kthread context, and only used with kernel preemption disabled,
>> this is okay.
>
> Kernel preemption is not explicitly disabled in the NX driver I think
> and
>
>>
>> If userspace can possibly copy/paste to the mappings or if you need to
>> sleep or call this from interrupt context, we need to work out how to
>> invalidate the copy buffer.
>
> user space cannot copy/paste to the mappings yet (that mechanism is
> further out).
>
> NX driver calls:
>
> vas_copy(&crb, ...);
> vas_paste(addr, ...);
>
> but not from an interrupt context. Can/should we disable premption between
> the copy/paste and to avoid having to invalidate the copy buffer?
Nick, Also we do not support 842 in user space. Only future NX gzip compression module.
If OK, will add disable premption for copy/paste. Thanks for review,
>
> Sukadev
>
prev parent reply other threads:[~2017-07-18 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 23:43 [PATCH V2 0/6] Enable NX 842 compression engine on Power9 Haren Myneni
2017-07-18 6:14 ` Nicholas Piggin
2017-07-18 18:06 ` Sukadev Bhattiprolu
2017-07-18 18:53 ` Haren Myneni [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=596E5940.7000207@linux.vnet.ibm.com \
--to=haren@linux.vnet.ibm.com \
--cc=ddstreet@ieee.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=nicholas.piggin@gmail.com \
--cc=sukadev@linux.vnet.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).