<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 6, 2015, at 2:31 AM, Sahasrabuddhe, Sameer <<a href="mailto:Sameer.Sahasrabuddhe@amd.com" class="">Sameer.Sahasrabuddhe@amd.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div bgcolor="#FFFFFF" text="#000000" class=""><blockquote class=" cite" id="mid_CAGCO0KjE2tyiAG_bCoELJgK6MpM4B4nQHaYyT__i5W33BdZ8jA_mail_gmail_com" cite="mid:CAGCO0KjE2tyiAG=bCoELJgK6MpM4B4nQHaYyT=-i5W33BdZ8jA@mail.gmail.com" type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">I probably *should* be in a position to be very interested in such a concept.... but honestly, I'm not. If I ever wanted to do something like this, I would just define the large-scale HPC system as the "system" and a single machine/node as some "local" scope.</div></div></div></div></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">I agree. The most accurate description of the highest scope is "address space scope", i.e., all threads that can access the address space being accessed. From that view, it does not matter if the threads are local, remote or situated on different devices, or such. It makes sense to not specify any keyword for this scope, and just say that "synchscope(0)" is default and need not be specified. Any other scope is an explicit optimization over a narrower set of threads.</span></div></div></blockquote></div><br class=""><div class="">I want to point out that “address space” is *not* sufficient for the highest scope. It’s entirely possible to have a host and and an accelerator that do not have shared address spaces, but do need to communicate, particularly in job management code where the accelerator talks directly to the host-side driver.</div><div class=""><br class=""></div><div class="">—Owen</div></body></html>