An location space defines the context in which a memory location add up. In the analogy of the individual's location, the location space would exist as an locality of locations, like a front yard, town, city, or even united states. Both addresses can be numerically a equivalent however refer to different locations, whenever it belong to different location spaces. This is similar to your computers location existence, say, "32, Main Street", when a second individual will reside within "32, Main Street" in a different town from either yours.

Case location spaces: Main memory (physical memory) Virtual memory I/O port space IP address House totals inside street addresses Street addresses within towns

Specific examples: a Linux kernel: Kernel virtual address space User virtual address space, accessed by the kernel across copy_to_user(), copy_from_user & similar functions I/O memory, accessed across readb(), writel(), memcpy_toio(), etc.

Address translation

Generally, items withinside the single location space come physically in a different location than items in another location space. E.g., "house number 101 South" in the single particular southwards street is entirely different from either any home total (nin just the 101st home) on a different southwards street.

Nevertheless, occasionally different location spaces overlap (a bit of physical location is around two location spaces). While overlapping location spaces are non aligned, translation is necessary. For even instance, virtual-to-physical location translation is necessary to translate addresses around the virtual memory location space to addresses in physical location space -- a single physical location, & of these or further numerically different virtual location, altogether refer to the equivalent physical byte of RAM.

de:Adressraum