From: "Felix Kühling" <felix.kuehling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: tstellar-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: Felix Kuehling <felix.kuehling-5C7GfCeVMHo@public.gmane.org>
Subject: Re: PCIe3 atomics requirement for amdkfd
Date: Sat, 23 Dec 2017 16:40:58 +0100 [thread overview]
Message-ID: <3f7e6fed-8668-b469-8813-e6677cb980ca@gmail.com> (raw)
In-Reply-To: <c2c34443-9ba1-661b-476d-b657a7ddfe85-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 726 bytes --]
As I understand it, it would require changes in the ROCr Runtime and in
the firmware (MEC microcode). It also changes the programming model, so
it may affect certain applications or higher level language runtimes
that rely on atomic operations.
Regards,
Felix
Am 19.12.2017 um 16:04 schrieb Tom Stellard:
> Hi,
>
> How hard of a requirement is PCIe3 atomics for dGPUs with the amdkfd
> kernel driver? Is it possible to make modifications to the runtime/kernel
> driver to drop this requirement?
>
> -Tom
> _______________________________________________
> amd-gfx mailing list
> amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 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-12-23 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:04 PCIe3 atomics requirement for amdkfd Tom Stellard
[not found] ` <c2c34443-9ba1-661b-476d-b657a7ddfe85-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-12-23 15:40 ` Felix Kühling [this message]
[not found] ` <3f7e6fed-8668-b469-8813-e6677cb980ca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-23 16:26 ` Alexander Kjeldaas
[not found] ` <CAHVSqQe1Tj+PnCR1h+HiHC=fXC81sUG4MXC7jWwmY+TomuU=9w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-24 10:07 ` Felix Kühling
2018-01-03 14:56 ` Tom Stellard
[not found] ` <a5d6072b-6fea-f161-3773-50f58766ed45-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-03 16:23 ` Liu, Shaoyun
[not found] ` <DM5PR12MB1179B2F3C378819556589747F41E0-2J9CzHegvk8p/eksZXEfgQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-03 16:40 ` Bridgman, John
2017-12-25 14:55 ` Luke A. Guest
[not found] ` <5a4b1672-4595-7e7f-0d76-9c721b61e98e-z/KZkw/0wg5BDgjK7y7TUQ@public.gmane.org>
2017-12-25 16:44 ` Bridgman, John
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=3f7e6fed-8668-b469-8813-e6677cb980ca@gmail.com \
--to=felix.kuehling-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=felix.kuehling-5C7GfCeVMHo@public.gmane.org \
--cc=tstellar-H+wXaHxf7aLQT0dZR+AlfA@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.