Talk:Memory address

message: We are doing an piece at uni on address-binding (runtime, compile-time, load-time) is it just me or does wikipedia lack anything on this? Paige Master 20:26, 13 June 2006 (UTC)
replies: text: 264 = 24·260 = 16·260. -- BenRG 14:16, 12 September 2007 (UTC)
thread_title: uni

message: Why are we using gibi instead of giga and exibi instead of exa.  —Preceding unsigned comment added by 67.110.32.253 (talk) 15:28, 31 August 2010 (UTC)
replies: text: The infix "bi" is a way of describing the binary proximation, so as to avoid confusion concerning what sizes are actually the case. A kibibyte is therefore 1024 (2^10) bytes, rather than 1000 (10^3). Mebi- is 2^20, Gibi- is 2^30 and so on. The reason for this, of course, is that computers work in terms of bits and bytes - a binary numeral system rather than a decimal numeral system - and physical increments are manufactured in the same fashion.  - 88.88.108.249 (talk) 09:56, 1 February 2011 (UTC)
thread_title: Spelling Clarification

message: In the final section, 'Virtual memory versus physical memory', this statement is made:
>When the program is actually executed, the virtual addresses are translated by the processor into real memory addresses.
I'm not sure that's accurate. I take 'processor' here to mean 'CPU'. My understanding is that the Memory management unit, rather than the CPU, translates virtual addresses into physical addresses. The MMU does that using a Translation Lookaside Buffer.  — Preceding unsigned comment added by PlaysWithLife (talk • contribs) 18:03, 29 August 2011 (UTC)
thread_title:  Dubious - virtual addresses translated by the processor 

message: Over 200 pages link to this page! Ideally, this article will provide something that satisfies them all!  That's a tall order, but a worthwhile goal. http://en.wikipedia.org/wiki/Special:WhatLinksHere/Memory_address Wbm1058 (talk) 21:25, 7 January 2012 (UTC)
thread_title: What links here

message: Well, of some sort covers a lot of ground, but it is not an adequate description for decimal machines such as the IBM 650 where a memory location held 10 bi-quinary coded decimal digits.  While individual digits might be "a binary number of some sort", the 10 digit memory location is base 10,  not 2; a decimal number irrespective of how the digits were encoded.50.136.247.190 (talk) 02:30, 31 October 2013 (UTC)
thread_title:  "Each memory location in a stored-program computer holds a binary number of some sort." 

message: Hello fellow Wikipedians,
I have just modified one external link on Memory address. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20121021050559/http://www.personal.psu.edu/dlw27/IST225/Hex_Dec_Memory.pdf to http://www.personal.psu.edu/dlw27/IST225/Hex_Dec_Memory.pdf
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 00:17, 5 September 2017 (UTC)
thread_title:  External links modified 

message: This article is not written well and should either be deleted or thoroughly clarified as soon as possible.  I am unable to do so because I do not know the subject well, but it is a very technical and important topic and as a reader, I find its mediocrity unacceptable.  I don't think there is any shame in removing it until it can be properly written because at this point it isn't clear enough to justify leaving up.  This criticism isn't directed at anyone in particular, including any original authors.  My only intention is to provide feedback as a concerned layperson and I understand that my words may be unpleasant to read.  — Preceding unsigned comment added by Jonassteinberg1 (talk • contribs) 02:14, 23 October 2017 (UTC)
thread_title:  This article is not well organized or written