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.
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.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}