Everything About ___
Live briefing

Everything about Mmap

Memory map - POSIX-compliant system call

In computing, mmap(2) is a POSIX-compliant Unix system call that maps files or devices into memory. It is a method of memory-mapped file I/O. It implements demand paging because file contents are not immediately read from disk and initially use no physical RAM at all. The actual reads from disk are performed after a specific location is accessed, in a lazy manner. After the mapping is no longer needed, the pointers must be unmapped with munmap(2). Protection information—for example, marking mapped regions as executable—can be managed using mprotect(2), and special treatment can be enforced using madvise(2). Wikipedia →

🧭 Start here: a 6-step reading path

  1. Read the overview: MmapA 5-minute orientation
  2. Skim a recent paper: Performance analysis of an energy-saving strategy in cloud data centers based on a MMAP[K]/M[K]/N1+N2 non-preemptive priority queueInfluential work since 2022
  3. Pick up a classic book: Linux System ProgrammingThe most-reprinted book on the subject
  4. Read the landmark paper: MmAP: Multi-Modal Alignment Prompt for Cross-Domain Multi-Task LearningCited 75 times
  5. Go sideways: /dev/zeroA closely related topic
  6. Go sideways: Select (Unix)A closely related topic

📖 Definitions

No dictionary entry for this exact phrase.

🏆 Landmark papers (most cited)

🆕 Influential since 2022

📚 Books worth reading

Ranked by number of editions on Open Library, a rough measure of how lasting a book is.

🔗 Related topics