Memory mapping: Difference between revisions

Revision as of 05:47, 5 September 2009

Revision as of 09:34, 20 April 2010

Line 1:

In computer system, memory mapping is a technique where the files are split in page sized chunks and copied to virtual memory so that the process can read the file contents as reading the memory. This provides very fast reading for file. Memory mapping permits different process to communicate via a shared file. Simply we can say, in memory mapping a file is mapped to virtual memory for faster access. In UNIX almost everything is a file. The devices are also represented as file in linux, you can find the devices on /dev in linux.

In [[computing]], '''memory mapping''' may refer to:

You can think of mapped memory as allocating a buffer to hold a file’s entire data, and then reading the file into the buffer and (if the buffer is modified) writing the buffer back out to the file.<ref>Advanced Linux Programming</ref>

* [[Memory-mapped file]], also known as <code>mmap()</code>

* [[Memory-mapped I/O]], an alternative to [[port I/O]]; a communication between CPU and peripheral device using the same instructions, and same bus, as between CPU and memory

* [[Virtual memory]], technique which gives an application program the impression that it has contiguous working memory, while in fact it is physically fragmented and may even overflow on to disk storage

<references/>http://download.lifenlivin.com/advanced-linux-programming.pdf

{{disambig}}

[[de:Memory mapping]]