Author(s):	PJ (Peter) Waskiewicz
Location	A1
Date	jan Wed 23	Days Raw Files
Start	10:40	First Raw Start	10:31
Duration	0:45:0	Offset	0:08:08
End	11:25	Last Raw End	11:31
Chapters	00:00 0:00:36 0:21:46 0:41:27
Total cuts_time	45 min.

https://2019.linux.conf.au/schedule/presentation/102/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Demystifying_interrupt_balancing_irqbalance.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	irqbalance is a userspace daemon that has been available for a number of years. Its main purpose is to make decisions on how to best balance interrupts within a system. Getting this "right" can be a challenge, since it needs to run on enterprise-level systems all the way to a mobile device. Taking things like NUMA locality, bus hierarchy, shared interrupts, cache locality, all into consideration, irqbalance is often misunderstood with how it works, what it can do, and what it cannot do. As co-maintainer of irqbalance, this talk is intended to pull the curtain back on how this whole framework operates. What pieces of the Linux kernel are involved in balancing interrupts, where policies are enforced, current best-known configurations, and future ideas to try and improve operation, are all things targeted with this talk. markdown
Comment:	production notes