BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2025//speaker//BQT7N8
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-devconf-cz-2025-WQDUDJ@pretalx.devconf.info
DTSTART;TZID=CET:20250613T110000
DTEND;TZID=CET:20250613T113500
DESCRIPTION:The Linux kernel RTNL mutex is the big lock protecting all of t
 he internal kernel data structures related to networking. While there is w
 ork underway in the upstream community to reduce its scope\, today this mu
 tex is a major source of scalability problems in the kernel networking sub
 system. It mostly affects control path operations (such as bringing networ
 k interfaces up and down)\, but unless care is taken to avoid it\, RTNL lo
 ck issues can also spill over into the data path\, causing intermittent st
 alls in networking applications that can be\nhard to debug.\n\nIn this tal
 k I will dive into techniques for debugging applications stalls caused by 
 contention on the RTNL lock\, using an example application that is derived
  from a real-world case. We will look at kernel tracing tools that can be 
 used to identify and debug such issues\, and talk about ways to mitigate t
 hem in the application. I will also briefly outline the upstream efforts t
 o reduce the scope of the RTNL in the kernel\, and how this will affect sy
 stems going forward.
DTSTAMP:20261117T201322Z
LOCATION:E105 (capacity 70)
SUMMARY:Beware of the kernel RTNL mutex - Toke Høiland-Jørgensen
URL:https://pretalx.devconf.info/devconf-cz-2025/talk/WQDUDJ/
END:VEVENT
END:VCALENDAR
