BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20211207T054807Z
LOCATION:227-228
DTSTART;TZID=America/Chicago:20211117T160000
DTEND;TZID=America/Chicago:20211117T163000
UID:submissions.supercomputing.org_SC21_sess176_pap327@linklings.com
SUMMARY:Paths to OpenMP in the Kernel
DESCRIPTION:Paper\n\nPaths to OpenMP in the Kernel\n\nMa, Wang, Nelson, Cu
 evas, Homerding...\n\nOpenMP implementations make increasing demands on th
 e kernel.  We take the next step and consider bringing OpenMP into the ker
 nel.  Our vision is that the entire OpenMP application, run-time system, a
 nd a kernel framework are interwoven to become the kernel, allowing the Op
 enMP implementation to take full advantage of the hardware in a custom man
 ner.  We compare and contrast three approaches to achieving this goal. The
  first, run-time in kernel (RTK), ports the OpenMP runtime to the kernel, 
 allowing any kernel code to use OpenMP pragmas.  The second, process in ke
 rnel (PIK), adds a specialized process abstraction for running user-level 
 OpenMP code within the kernel.  The third, custom compilation for kernel (
 CCK), compiles OpenMP into a form that leverages the kernel framework with
 out any intermediaries.  We describe the design and implementation of thes
 e approaches, and evaluate them using NAS and other benchmarks.\n\nTag: Re
 producibility Badge, System Software and Runtime Systems\n\nRegistration C
 ategory: Tech Program Reg Pass\n\nReproducibility Badges: Artifact Availab
 le
END:VEVENT
END:VCALENDAR