Talk:Flat memory model
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
|
|
Application vs system programming[edit]
Although logical–physical distinction is mentioned, it remains unclear, what means "to address sequentially all of the available memory locations" in the context of a multitasking memory-protecting operating system. The address space of an application process unlikely may be contiguous for some technical reasons. Incnis Mrsi (talk) 08:44, 10 April 2012 (UTC)
segmented memory model[edit]
I renamed this section as "x86..." because other systems, for example burroughs and Multics function differently and don't have the problems cited. Peter Flass (talk) 17:02, 3 September 2013 (UTC)
Paged memory model[edit]
I don' get why this is a "memory model" at all - it should be transparent at the application level. Peter Flass (talk) 11:56, 6 September 2013 (UTC)