Transcription of 10 Things Every Linux Programmer Should Know
{{id}} {{{paragraph}}}
ResearchLabsLinuxKernelWorkshop, March2004 aboutUserspacevs. kernelspaceMemory allocationProcessesvs. threadsNPTL- Native POSIXT hreadsLibraryOptimizationUsetherightabst ractionlayerforthejobWhy 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().Thebiggestdif ferencebetweenuserspaceandkernelspaceis conceptual-theprogrammer s stateof , March2004 a library function,implementedin thestandardC library.
What this talk is about This talk is about common misconceptions, and things I think every Linux programmer should know. This talk is about learning from other people’s
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}