Author(s):	Michael Kerrisk
Location	MCC6
Date	jan Wed 30	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	1:40:00	Offset	None
End	12:20	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30020/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf An_Introduction_to_Linux_IPC_Facilities.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:	Pipes, FIFOs, signals, datagram and stream sockets (and sockets in the Unix versus Internet domains), file locks (various kinds!), environment variables, memory mappings, event file descriptors (eventfd), pseudo-terminals, message queues, semaphores, shared memory, and good old regular files... The range of interprocess communication and synchronization (often referred to collectively as IPC) facilities available on Linux can at first seem bewildering. Which facilities should an application use? This tutorial provides an overview of each of the IPC facilities, showing the features that the different facilities have in common, and the features that distinguish them. The aims of this tutorial are to provide developers with examples of the use of each of the IPC facilities and the beginnings of a roadmap to help decide which IPC facilities are likely to be most suitable when writing new applications. I'll compare different IPC facilities using measures such as portability, flexibility, ease of use, operational limits, configurability, persistence (lifetime), access control, integration with the traditional Unix "everything is a file" model and the UNIX/Linux API in general, and specific functional advantages and disadvantages. I'll also briefly consider whether one can make any general statements about relative performance of different IPC facilities. Although aimed primarily at developers, other participants (e.g., system administrators) may find the tutorial useful for gaining greater insight into the operation, configuration, and management of the various IPC facilities. A reading knowledge of C will be useful. markdown
Comment:	production notes