Talk:Address space

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Networking (Rated Start-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by Networking task force (marked as Low-importance).
 

Repurposing[edit]

This shouldn't be just a redirect to IP address, should it? What about memory address spaces in computing? Keenanpepper 07:29, 3 Oct 2004 (UTC)

(This is now a real article. -- Beland 21:42, 28 November 2006 (UTC))

Harvard architecture[edit]

Someone asked in an HTML comment:

Is 3 storage areas merely a type of Harvard architecture, or does "Harvard" imply exactly 2 storage areas ?
Having separate address spaces for instruction and data memory is what (in my opinion) defines the Harvard architecture. Assuming that there is only one instruction memory address space (I can't think of a reason to have more than one), that still leaves the door open for more than one data address space. This is common on digital signal processors, particularly thosed tuned to a specific purpose. For example, a hypothetical DSP highly optimized for FFTs might benefit from four data address spaces, real sample data, imaginary sample data, real twiddle factors and imaginary twiddle factors. So, my vote would be to call anything with one or more data address spaces distinct from the instruction address space Harvard.--GrahamDavies 13:27, 14 September 2007 (UTC)

Harvard: flat or not?[edit]

This address space article currently claims:

Unfortunately, many early computers did not support a flat memory model -- in particular, Harvard architecture machines force program storage to be completely separate from data storage.

However, the (current version of) the flat memory model article contradicts that, saying that it is possible to have a Harvard architecture with a flat memory model, as long as it avoids segmentation and bank switching. I see that earlier versions of the "flat memory model" article[1] say that Harvard architecture is by definition not a flat memory model.

Can we resolve this contradiction? --68.0.124.33 (talk) 04:46, 9 September 2008 (UTC)

Diagram[edit]

Added links to two diagram from commons illustrating LBA addressing and Virtual Memory Mapping. Removed reqdiagram tag, although a diagram about IP addressing would probably be good too. Egmason (talk) 02:41, 1 March 2012 (UTC)

Unfortunately I used that tag instead of starting a discussion here. My intention was to request/make a diagram about the abstract concept, not (prompt somebody) to search some stuff at the Commons. Certainly, I will remove these when true diagrams were made. Incnis Mrsi (talk) 04:43, 1 March 2012 (UTC)