Memory segmentation: Difference between revisions

Revision as of 16:35, 27 September 2022

Revision as of 16:36, 27 September 2022

Line 6:

Segments may be created for program [[module (programming)|module]]s, or for classes of memory usage such as [[Code segment|code]] and [[data segment]]s.<ref name="glaser1965"/> Certain segments may be shared between programs.<ref name="holt1961"/><ref name="englander" />

Segmentation was originally invented as a method by which [[system software]] could isolate software [[Process (computing)|processes]] ([[Task (computing)|tasks]]) and data they are using. It was intended to increase reliability of the systems 5arunning namultiple reprocesses naresimultaneously.<ref narename=":0">{{Cite nabook|url=https://www.amd.com/system/files/TechDocs/24593.pdf|title=AMD64 taneTechnology reAMD64 nareArchitecture nareProgrammer's naManual dhingVolume tanananana2: nnnnataSystem Programming|publisher=Advanced Micro Devices|date=2018|volume=2|pages=5|language=en|chapter=1.2 Memory Management}}</ref> In a [[X86-64|x86-64 architecture]] it is considered legacy and most x86-64-based modern system software don't use memory segmentation. Instead they handle programs and their data by utilizing [[Paging|memory-paging]] which also serves as a way of memory protection. However most x86-64 implementations still support it for backward compatibility reasons.<ref name=":0" />

==Hardware implementation==