Talk:Memory mapping

Mapping of files into memory

This article should probably also cover mapping files to a process's memory space, as in the Unix mmap syscall. Or perhaps create a disambiguation page here and discuss them in separate articles. -- intgr 11:19, 28 December 2006 (UTC)[reply]

Suggested change to disambiguation page

This article is not well named, and as intgr suggests, a change to a disambiguation page would be suitable as the concepts of memory mapping in relation to both files and I/O are already discussed (with some room for improvement) in their own sections; see memory mapped I/O and memory-mapped file. Moggie2002 11:11, 17 January 2007 (UTC)[reply]

Inclusion

The concept of "Memory Mapping" is designing the map of the addresses and deciding where, in this map, will be the RAM, the ROM or the I/O devices. Actually, the I/O devices have their own map nowadays. I recomend this article to be included in another one named "Decoding of Microprocessors". This article may explain ( more deeply ) how to connect the address and data buses to the different devices and what electronical elements you may use to manage that. —The preceding unsigned comment was added by Alsolike (talkcontribs) 12:24, 2 May 2007 (UTC).[reply]

Dabconcept

As a dab it fails as all are examples of a broad concept per WP:DABCONCEPT. The older version [1] may have some useful text for fleshing out, if there's concensus for fixing this bad dab. Widefox; talk 08:35, 1 April 2016 (UTC)[reply]

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.