BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//ASG2019//UJNAGB
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-ASG2019-TPS8TS@cfp.all-systems-go.io
DTSTART;TZID=CET:20190921T110000
DTEND;TZID=CET:20190921T114000
DESCRIPTION:Traditionally processes are identified globally via process ide
 ntifiers (PIDs). Due to how pid allocation works the kernel is free to rec
 ycle PIDs once a process has been reaped. As such\, PIDs do not allow anot
 her process to maintain a private\, stable reference on a process. On syst
 ems under pressure it is thus possible that a PID is recycled without othe
 r (non-parent) processes being aware of it. This becomes rather problemati
 c when (non-parent) processes are in charge of managing other processes as
  is the case for system managers or userspace implementations of OOM kille
 rs.\n\nOver the last months we have been working on solving these and othe
 r problems by introducing pidfds – process file descriptors. Among other
  nice properties\, the allow callers to maintain a private\, stable refere
 nce on a process.\n\nIn this talk we will look at challenges we faced and 
 the different approaches people pushed for. We will see what already has b
 een implement and pushed upstream\, look into various implementation detai
 ls and outline what we have planned for the future.
DTSTAMP:20260521T075308Z
LOCATION:Loft
SUMMARY:pidfds: Process file descriptors on Linux - Christian Brauner
URL:https://cfp.all-systems-go.io/ASG2019/talk/TPS8TS/
END:VEVENT
END:VCALENDAR