<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://debianws.lexgopc.com/wiki143/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=103.97.2.161</id>
	<title>wiki143 - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://debianws.lexgopc.com/wiki143/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=103.97.2.161"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Special:Contributions/103.97.2.161"/>
	<updated>2026-05-15T05:37:12Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://debianws.lexgopc.com/wiki143/index.php?title=Physical_address&amp;diff=2905992</id>
		<title>Physical address</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Physical_address&amp;diff=2905992"/>
		<updated>2025-01-05T19:40:58Z</updated>

		<summary type="html">&lt;p&gt;103.97.2.161: /* Use by other devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{About|computer memory addressing|the meaning in networking|MAC address|addresses of physical locations|Address}}&lt;br /&gt;
[[Image:Virtual address space and physical address space relationship.svg|thumb|300px|Diagram of relationship between the virtual and physical address spaces]]&lt;br /&gt;
In [[computing]], a &#039;&#039;&#039;physical address&#039;&#039;&#039; (also &#039;&#039;&#039;real address&#039;&#039;&#039;, or &#039;&#039;&#039;binary address&#039;&#039;&#039;), is a [[memory address]] that is represented in the form of a [[binary number]] on the [[address bus]] circuitry in order to enable the [[Bus (computing)|data bus]] to access a &#039;&#039;particular&#039;&#039; storage cell of [[main memory]], or a register of [[memory-mapped I/O]] device.&lt;br /&gt;
&lt;br /&gt;
==Use by central processing unit==&lt;br /&gt;
In a computer supporting [[virtual memory]], the term &#039;&#039;physical address&#039;&#039; is used mostly to differentiate from a &#039;&#039;[[virtual address space|virtual address]]&#039;&#039;.  In particular, in computers utilizing a [[memory management unit]] (MMU) to translate memory addresses, the virtual and physical addresses refer to an address before and after translation performed by the MMU, respectively.&amp;lt;ref&amp;gt;{{cite web&lt;br /&gt;
 | url = http://cseweb.ucsd.edu/classes/su09/cse120/lectures/Lecture7.pdf&lt;br /&gt;
 | title = Lecture 7: Memory Management&lt;br /&gt;
 | work = CSE 120: Principles of Operating Systems&lt;br /&gt;
 | year = 2009 | access-date = 2013-12-04&lt;br /&gt;
 | author = Frank Uyeda | publisher = UC San Diego&lt;br /&gt;
 }}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Unaligned addressing===&lt;br /&gt;
Depending upon its underlying [[computer architecture]], the performance of a computer may be hindered by &#039;&#039;unaligned&#039;&#039; access to memory.  For example, a [[16-bit computing|16-bit]] computer with a 16-bit memory data bus, such as [[Intel 8086]], generally has less [[computational overhead|overhead]] if the access is aligned to an even address. In that case fetching one 16-bit value requires a single memory read operation, a single transfer over a data bus.&amp;lt;ref name=&amp;quot;lwn-alignment&amp;quot;&amp;gt;{{cite web&lt;br /&gt;
 | url = https://lwn.net/Articles/260832/&lt;br /&gt;
 | title = Memory access and alignments&lt;br /&gt;
 | date = 2007-12-04 | access-date = 2013-12-04&lt;br /&gt;
 | author = Daniel Drake | publisher = [[LWN.net]]&lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web&lt;br /&gt;
 | url = https://www.kernel.org/doc/Documentation/unaligned-memory-access.txt&lt;br /&gt;
 | title = Documentation/unaligned-memory-access.txt&lt;br /&gt;
 | access-date = 2013-12-04&lt;br /&gt;
 | author1 = Daniel Drake | author2 = Johannes Berg&lt;br /&gt;
 | publisher = kernel.org&lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the 16-bit data value starts at an odd address, the processor may need to perform two memory read cycles to load the value into it, i.e. one for the low address (throwing away half of it) and then a second read cycle to load the high address (throwing away again half of the retrieved data).  On some [[Processor (computing)|processors]], such as the [[Motorola 68000]] and [[Motorola 68010]] processors, and [[SPARC]] processors, unaligned memory accesses will result in an exception being raised (usually resulting in a software exception, such as [[POSIX]]&#039;s [[SIGBUS]], being raised).&amp;lt;ref name=&amp;quot;lwn-alignment&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Use by other devices==&lt;br /&gt;
{{expand section|date=January 2012}}&lt;br /&gt;
&lt;br /&gt;
The [[direct memory access]] (DMA) feature allows other devices in the [[mother board]] besides the CPU to address the main memory.  Such devices, therefore, also need to have a knowledge of physical addresses.&lt;br /&gt;
&lt;br /&gt;
The [[memory-mapped I/O]] addresses are also physical addresses, which may be accessed by the [[device driver]]s in an operating system.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
* [[Address constant]]&lt;br /&gt;
* [[Addressing mode]]&lt;br /&gt;
* [[Address space]]&lt;br /&gt;
* [[Page address register]]&lt;br /&gt;
* [[Pointer (computer programming)]]&lt;br /&gt;
* [[Primary storage]], also known as &#039;&#039;main memory&#039;&#039;&lt;br /&gt;
* [[Virtual memory]]&lt;br /&gt;
** [[Virtual address]], also known as [[logical address]]&lt;br /&gt;
** [[Page table]]&lt;br /&gt;
** [[Memory management unit]] (MMU)&lt;br /&gt;
* [[Gray code addressing]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
{{Data types}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Computer memory]]&lt;br /&gt;
[[Category:Virtual memory]]&lt;br /&gt;
[[Category:Data types]]&lt;/div&gt;</summary>
		<author><name>103.97.2.161</name></author>
	</entry>
</feed>