[Beowulf] Frontier Announcement
Jeffrey Layton
laytonjb at gmail.com
Wed May 8 14:56:18 PDT 2019
I wrote some OpenACC articles for HPC Admin Magazine. A number of
pro-OpenMP people attacked me on twitter (you know, OpenACC sucks, OpenMP
is great). I received a private email threatening to kill me and my family
if I didn't stop writing about OpenACC. Given your pro-OpenMP, anti-OpenACC
stance, using the same tone as the threatening email, I wondered if that
email came from you.
On Wed, May 8, 2019, 17:48 Richard Walsh <rbwcnslt at gmail.com> wrote:
>
> Huh ... ?? Weird, scary ...
>
> Just MHO. Dropping off this thread now ...
>
> rbw
>
> Sent from my iPhone
>
> On May 8, 2019, at 4:29 PM, Jeffrey Layton <laytonjb at gmail.com> wrote:
>
> I was just pointing out that gcc has Open ACC capability on AMD GPUs.
>
> I didn't realize you part of the OpenMP Nazis. Were you the one that
> threatened me and my family because I wrote about OpenACC?
>
>
>
> On Wed, May 8, 2019, 15:48 Richard Walsh <rbwcnslt at gmail.com> wrote:
>
>>
>> Jeffry/All,
>>
>> Yes ... but given the choice of using OpenACC or OpenMP (if you are not
>> going to write CUDA-HIP code for that extra 10% of performance) which
>> captures most (all?) of the features of OpenACC, is a standard likely to
>> outlive OpenACC, and should run on any vendor’s accelerators, including
>> whatever Intel comes up with ... why would you write in OpenACC ... ??
>>
>> GNU supports OpenMP too ... in my view, PVM is to MPI as OpenACC is to
>> OpenMP 4.5-5.0 ...
>>
>> Cheers!
>>
>> rbw
>>
>> Sent from my iPhone
>>
>> On May 8, 2019, at 2:36 PM, Jeffrey Layton <laytonjb at gmail.com> wrote:
>>
>> Don't forget that gcc supports both NV and AMD GPUs with OpenACC. That's
>> one of the lead compilers listed on the Frontier specs.
>>
>> Jeff
>>
>>
>> On Wed, May 8, 2019 at 3:29 PM Richard Walsh <rbwcnslt at gmail.com> wrote:
>>
>>>
>>> All,
>>>
>>> Cray has deprecated support for in OpenACC in light of the OpenMP 4.5
>>> and 5.0 standards, and their target and data directives. NVIDIA’s PGI
>>> Compiler group will keep OpenACC going for a while, but on AMD devices ...
>>> maybe not. That Cray will support only OpenMP on Frontier seems to be a
>>> logical certainty.
>>>
>>> So if you or yours want to run at speed on Frontier you should bone up
>>> on ROCm, HIP and OpenMP 4.5-5.0 ...
>>>
>>> :-)
>>>
>>> Cheers!
>>>
>>> rbw
>>>
>>> Sent from my iPhone
>>>
>>> > On May 8, 2019, at 12:47 PM, Jörg Saßmannshausen <
>>> sassy-work at sassy.formativ.net> wrote:
>>> >
>>> > Dear all,
>>> >
>>> > I think the answer to the question lies here:
>>> >
>>> > https://en.wikipedia.org/wiki/OpenACC
>>> >
>>> > As I follow these things rather loosely, my understanding was that
>>> OpenACC
>>> > should run on both nVidia and other GPUs. So maybe that is the reason
>>> why it
>>> > is a 'pure' AMD cluster where both GPUs and CPUs are from the same
>>> supplier?
>>> > IF all of that is working out and if it is really true that you can
>>> compile
>>> > and run OpenACC code on both types of GPUs, it would a be big win for
>>> AMD.
>>> >
>>> > Time will tell!
>>> >
>>> > All the best from my TARDIS!
>>> >
>>> > Jörg
>>> >
>>> > Am Dienstag, 7. Mai 2019, 16:59:48 BST schrieben Sie:
>>> >>> I think it is interesting that they are using AMD for
>>> >>>
>>> >>> both the CPUs and GPUs
>>> >>
>>> >> I agree. That means a LOT of codes will have to be ported from CUDA to
>>> >> whatever AMD uses. I know AMD announced their HIP interface to convert
>>> >> CUDA code into something that will run on AMD processors, but I don't
>>> >> know how well that works in theory. Frankly, I haven't heard anything
>>> >> about it since it was announced at SC a few years ago.
>>> >>
>>> >> I would not be surprised if AMD pursued this bid quite agressively,
>>> >> possibly at a significant loss, for the opportunity to prove their
>>> GPUs
>>> >> can compete with NVIDIA and demonstrate that codes can be successfully
>>> >> converted from CUDA to something AMD GPUs can use to demonstrate GPU
>>> >> users don't need to be locked in to a single vendor. If so, this could
>>> >> be a costly gamble for the DOE and AMD, but if it pays off, I imagine
>>> it
>>> >> could change AMD's fortunes in HPC.
>>> >>
>>> >> "Win on Sunday, sell on Monday" doesn't apply just to cars.
>>> >>
>>> >> Prentice
>>> >>
>>> >>> On 5/7/19 4:43 PM, Jörg Saßmannshausen wrote:
>>> >>> Hi Prentice,
>>> >>>
>>> >>> that looks interesting and I hope it means I will finally get the
>>> neutron
>>> >>> structure which was measured last year there! :-)
>>> >>>
>>> >>> On a more serious note: I think it is interesting that they are
>>> using AMD
>>> >>> for both the CPUs and GPUs. It sounds at least very fast of what they
>>> >>> want to build, lets hope their design will work as planned as well.
>>> >>>
>>> >>> All the best from London
>>> >>>
>>> >>> Jörg
>>> >>>
>>> >>> Am Dienstag, 7. Mai 2019, 10:32:42 BST schrieb Prentice Bisbal via
>>> > Beowulf:
>>> >>>> ORNL's Frontier System has been announced:
>>> >>>>
>>> >>>>
>>> https://www.hpcwire.com/2019/05/07/cray-amd-exascale-frontier-at-oak-ridg
>>> >>>> e/
>>> >
>>> > _______________________________________________
>>> > Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin
>>> Computing
>>> > To change your subscription (digest mode or unsubscribe) visit
>>> https://beowulf.org/cgi-bin/mailman/listinfo/beowulf
>>> _______________________________________________
>>> Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin Computing
>>> To change your subscription (digest mode or unsubscribe) visit
>>> https://beowulf.org/cgi-bin/mailman/listinfo/beowulf
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://beowulf.org/pipermail/beowulf/attachments/20190508/f2f95382/attachment.html>
More information about the Beowulf
mailing list