0Pricing
Assembly Language & x86 Low-Level Systems Programming · Leçon

Pagination et unité de gestion de la mémoire (MMU)

Comprenez comment la MMU x86 traduit les adresses virtuelles en adresses physiques à l’aide des tables et des répertoires de pages.

Pagination et unité de gestion de la mémoire (MMU) est une leçon Assembly Language & x86 Low-Level Systems Programming gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Assembly Language & x86 Low-Level Systems Programming, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Assembly Language & x86 Low-Level Systems Programming comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

What is Paging?

Welcome! Today we'll explore Paging, a crucial memory management technique in x86 systems. It's how your computer handles memory safely and efficiently.

Paging allows programs to think they have a huge, continuous block of memory, even if the physical RAM is fragmented or smaller than what the program needs.

Virtual vs. Physical Address

When a program runs, it uses virtual addresses. These are logical addresses that the program 'sees' and uses to refer to data and instructions.

However, the CPU and actual RAM hardware use physical addresses. Paging is the system that translates virtual addresses into physical addresses.

The MMU's Role

The translation from virtual to physical addresses is handled by a special hardware component inside the CPU called the Memory Management Unit (MMU).

The MMU acts like a super-fast translator, ensuring that every memory access from a program goes to the correct physical location in RAM, or signals an error if it's an invalid access.

Pages and Page Frames

For paging to work, memory is divided into fixed-size blocks:

  • Pages: These are the blocks of virtual memory that a program sees.
  • Page Frames: These are the blocks of physical memory (RAM).

On x86 systems, a common page size is 4 Kilobytes (4KB). The MMU translates virtual pages to physical page frames.

Introducing Page Tables

How does the MMU know which virtual page maps to which physical page frame? It uses data structures called page tables.

A page table is essentially an array where each entry maps a virtual page number to its corresponding physical page frame address. Each running process has its own set of page tables.

Multi-Level Paging: Page Directories

For very large virtual address spaces (like 32-bit or 64-bit systems), a single page table would be enormous. To manage this, x86 uses a multi-level paging hierarchy.

The first level is the Page Directory. It doesn't point directly to page frames, but to other Page Tables. These secondary tables then point to the actual physical page frames.

The Address Translation Process

Let's simplify the 32-bit address translation process:

  1. The CPU generates a virtual address.
  2. The MMU uses the upper bits of this address to find an entry in the Page Directory.
  3. That entry points to a specific Page Table.
  4. The MMU uses middle bits of the virtual address to find an entry in that Page Table.
  5. This entry contains the physical address of the Page Frame.
  6. The lower bits of the original virtual address (the offset) are added to the page frame address to get the final physical address.

CR3: The Paging Root

How does the MMU know where the Page Directory is for the current process?

The CPU has a special control register called CR3. This register holds the physical address of the current Page Directory Base Register (PDBR). It tells the MMU exactly where to start looking for the page directory.

PTE Flags and Permissions

Each entry in a Page Table (a PTE - Page Table Entry) contains more than just the physical address. It also has various flags:

  • Present: Is the page currently in physical memory?
  • Read/Write: Can the page be written to?
  • User/Supervisor: Can user-mode programs access this page?
  • Accessed: Has the page been accessed recently?
  • Dirty: Has the page been written to since it was loaded?

These flags are vital for memory protection and virtualization.

Benefits of Paging

Paging is fundamental to modern operating systems due to its many benefits:

  • Memory Protection: Isolates processes, preventing them from corrupting each other's memory.
  • Virtual Memory: Allows programs to use more memory than physically available by swapping pages to disk.
  • Memory Sharing: Multiple processes can share the same physical pages (e.g., for shared libraries or inter-process communication).
  • Relocation: Programs can be loaded anywhere in physical memory; the MMU handles the mapping.

Paging Knowledge Check

Which of the following best describes the primary function of the Memory Management Unit (MMU) in an x86 system?

Paging & MMU Recap

Great job! You've learned about the critical role of Paging and the MMU.

  • Programs use virtual addresses, while hardware uses physical addresses.
  • The MMU translates these addresses using Page Directories and Page Tables.
  • Memory is divided into pages (virtual) and page frames (physical).
  • The CR3 register points to the current Page Directory.
  • PTE flags control permissions and page status.

This system provides essential memory protection, virtual memory, and flexible memory management for all modern operating systems.

Questions Fréquemment Posées

La leçon « Pagination et unité de gestion de la mémoire (MMU) » est-elle gratuite ?

Oui — le texte complet de « Pagination et unité de gestion de la mémoire (MMU) » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Assembly Language & x86 Low-Level Systems Programming, passe à CoddyKit PRO. Le cours Assembly Language & x86 Low-Level Systems Programming comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Pagination et unité de gestion de la mémoire (MMU) » ?

Comprenez comment la MMU x86 traduit les adresses virtuelles en adresses physiques à l’aide des tables et des répertoires de pages. Tu pratiques Assembly Language & x86 Low-Level Systems Programming avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Assembly Language & x86 Low-Level Systems Programming ?

Aucune expérience préalable n'est requise. Assembly Language & x86 Low-Level Systems Programming sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.

Combien de temps prend la leçon « Pagination et unité de gestion de la mémoire (MMU) » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Assembly Language & x86 Low-Level Systems Programming ?

Oui. Chaque leçon Assembly Language & x86 Low-Level Systems Programming inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Pagination et unité de gestion de la mémoire (MMU)
  2. Anneaux de protection et privilèges
  3. Hyperviseurs et bases de la virtualisation
  4. Segmentation et table globale des descripteurs (GDT)
← Retour à Assembly Language & x86 Low-Level Systems Programming