10 Things Every Linux Programmer Should Know

← Back to document page

ResearchLabsLinuxKernelWorkshop, March2004 aboutUserspacevs. kernelspaceMemory allocationProcessesvs. threadsNPTL- Native POSIXThreadsLibraryOptimizationUsetherig htabstractionlayerforthejobWhy codingstyleis importantWhy youshouldalwayscheck forerrorsTherealcostof softwaredevelopmentPortabilityLinuxKerne lWorkshop, March2004 aboutThistalkis aboutcommonmisconceptions, andthingsIthinkevery aboutlearningfromotherpeople abouthow to s aboutknowinghow thingswork; Knowinghowthingswork opinions, andmineonly. Feelfreeto .LinuxKernelWorkshop, March2004 processis executingeitherin userspace, orin kernelspace. Dependingonwhichpriviledges, addressspaceandaddress(EIP)a processis executingin,we saythatit is eitherin userspace, userspace, a processhasnormalpriviledgesandcanandcan tdocertainthings. Whenexecutingin kernelspace, a processhaseverypriviledge, , suchasprocessesusingiopl().

think every Linux programmer should know. This talk is about learning from other people’s experience and mistakes. This talk is about how to write better software. It’s about knowing how things work; Knowing how things work lets us embrace and extend Linux.

  Linux, Should, Programmer, Know, Every, Things, Every linux programmer should know, 10 things every linux programmer should know