All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bridgman, John" <John.Bridgman-5C7GfCeVMHo@public.gmane.org>
To: "Luke A. Guest" <laguest-z/KZkw/0wg5BDgjK7y7TUQ@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: RE: PCIe3 atomics requirement for amdkfd
Date: Mon, 25 Dec 2017 16:44:01 +0000	[thread overview]
Message-ID: <CY4PR12MB13493E4F4D9467C61B07906CE8010@CY4PR12MB1349.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5a4b1672-4595-7e7f-0d76-9c721b61e98e-z/KZkw/0wg5BDgjK7y7TUQ@public.gmane.org>

Let's separate out OpenCL from HCC/HIP and the rest of the ROCm stack. 

We are working on a solution to deliver OpenCL without requiring atomics, but not the rest of the ROCm stack.

>-----Original Message-----
>From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On Behalf Of
>Luke A. Guest
>Sent: Monday, December 25, 2017 9:55 AM
>To: amd-gfx@lists.freedesktop.org
>Subject: Re: PCIe3 atomics requirement for amdkfd
>
>Hi,
>
>I have to agree here. At least there should be a non-PCIe-3.0 pathway which
>implements them on the CPU, I mean, they're fairly simple atomics, CAS,
>SWAP, FetchAdd.
>
>What AMD have actually done is royally screwed over anyone with an FX
>chipset, i.e. no OpenCL - the open source AMD one requires ROCm, they
>abandoned Clover, maybe PoCL will work? Who knows.
>
>
>On 19/12/17 15:04, Tom Stellard wrote:
>> 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@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
>_______________________________________________
>amd-gfx mailing list
>amd-gfx@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2017-12-25 16:44 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
     [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 [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=CY4PR12MB13493E4F4D9467C61B07906CE8010@CY4PR12MB1349.namprd12.prod.outlook.com \
    --to=john.bridgman-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=laguest-z/KZkw/0wg5BDgjK7y7TUQ@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.