BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
X-LIC-LOCATION:Europe/Stockholm
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20190719T085744Z
LOCATION:HG F 3
DTSTART;TZID=Europe/Stockholm:20190613T151500
DTEND;TZID=Europe/Stockholm:20190613T154500
UID:submissions.pasc-conference.org_PASC19_sess130_msa135@linklings.com
SUMMARY:Utility Thread Interface: A System-Wide Resource Management Framew
 ork for Helper/Compute Threads
DESCRIPTION:Minisymposium\nComputer Science and Applied Mathematics\n\nUti
 lity Thread Interface: A System-Wide Resource Management Framework for Hel
 per/Compute Threads\n\nTakagi, Gerofi, Pedretti, Riesen\n\nThe processor a
 nd memory structure in HPC system is getting more and more complex. For ex
 ample, tens of cores and a memory module comprises a NUMA-node, and some o
 f them are connected by network-on-chip. Cores in one NUMA-node could
  even be divided into two types, i.e. those dedicated to system servi
 ces and computation. One way to exploit this trend is the helper thread te
 chnique, in which helper threads, e.g., MPI asynchronous progress thr
 eads, are put to the system service cores to help compute tasks. However, 
 there is a portability issue, i.e., there is no portable interface for app
 lication/run-time to tell OS about the compute / non-compute distinction, 
 preferred resource location and scheduling policy. To respond to&nbsp
 ;the issue, we introduce a portable interface, called Utility Thread Offlo
 ading Interface (UTI). The talk describes the API and demonstrates it
 s benefits through application use cases.
END:VEVENT
END:VCALENDAR