From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: "Kasiviswanathan,
Harish" <Harish.Kasiviswanathan-5C7GfCeVMHo@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Support for amdgpu VM update via CPU on large-bar systems
Date: Fri, 12 May 2017 16:25:30 +0800 [thread overview]
Message-ID: <5915717A.3000209@amd.com> (raw)
In-Reply-To: <DM3PR1201MB10382F282D646D630708246D8CEF0-BBcFnVpqZhWjUUTFdQAMQmrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 986 bytes --]
On 2017年05月10日 05:47, Kasiviswanathan, Harish wrote:
> Hi,
>
> Please review the patch set that supports amdgpu VM update via CPU. This feature provides improved performance for compute (HSA) where mapping / unmapping is carried out (by Kernel) independent of command submissions (done directly by user space). This version doesn't support shadow copy of VM page tables for CPU based update.
I think your improved performance is from less waiting for cs,
generally, SDMA engine updating page table is faster than CPU, otherwise
we don't need sdma for updating PT.
So whether your this improvement proves we have some redundant sync when
mapping / unmapping, if yes, we should fix that, then not sure if CPU
method is need or not.
Regards,
David Zhou
>
> Best Regards,
> Harish
>
>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[-- Attachment #1.2: Type: text/html, Size: 1985 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-05-12 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 21:47 Support for amdgpu VM update via CPU on large-bar systems Kasiviswanathan, Harish
[not found] ` <DM3PR1201MB10382F282D646D630708246D8CEF0-BBcFnVpqZhWjUUTFdQAMQmrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-12 8:25 ` zhoucm1 [this message]
[not found] ` <5915717A.3000209-5C7GfCeVMHo@public.gmane.org>
2017-05-12 8:33 ` Christian König
[not found] ` <21e206ed-8d60-450f-6d23-e01c68c5ad73-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-05-12 8:37 ` zhoucm1
[not found] ` <59157453.8010308-5C7GfCeVMHo@public.gmane.org>
2017-05-12 8:43 ` Christian König
[not found] ` <b82fc6cd-c19e-85c2-8628-89c2cb10c5c0-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-05-12 8:44 ` zhoucm1
2017-05-12 19:25 ` Felix Kuehling
[not found] ` <9f9f1e0c-caf6-7233-03c6-59196f672a72-5C7GfCeVMHo@public.gmane.org>
2017-05-13 9:08 ` Christian König
-- strict thread matches above, loose matches on Subject: below --
2017-05-09 18:34 Kasiviswanathan, Harish
[not found] ` <DM3PR1201MB103847C11F89904752F962768CEF0-BBcFnVpqZhWjUUTFdQAMQmrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-10 7:23 ` Christian König
[not found] ` <1b144623-3315-5dd7-fcc7-3be9e24e0f21-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-05-10 18:50 ` Kasiviswanathan, Harish
[not found] ` <DM3PR1201MB1038AAC8F7B04B7F3E015FE88CEC0-BBcFnVpqZhWjUUTFdQAMQmrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-10 19:22 ` Christian König
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=5915717A.3000209@amd.com \
--to=david1.zhou-5c7gfcevmho@public.gmane.org \
--cc=Harish.Kasiviswanathan-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.