From d25316c60085b42f9a7919dd03a7fa015d21fe4b Mon Sep 17 00:00:00 2001 From: ruxbin Date: Tue, 28 Feb 2023 13:27:08 +0800 Subject: [PATCH] Update linux-mm-1.md --- MM/linux-mm-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MM/linux-mm-1.md b/MM/linux-mm-1.md index 79db444..62c0e0a 100644 --- a/MM/linux-mm-1.md +++ b/MM/linux-mm-1.md @@ -124,7 +124,7 @@ Here we can see initialization of the `memblock` structure which has the same na You can see that it depends on `CONFIG_ARCH_DISCARD_MEMBLOCK`. If this configuration option is enabled, memblock code will be put into the `.init` section and will be released after the kernel is booted up. -Next we can see the initialization of the `memblock_type memory`, `memblock_type reserved` and `memblock_type physmem` fields of the `memblock` structure. Here we are interested only in the `memblock_type.regions` initialization process. Note that every `memblock_type` field is initialized by and array of `memblock_region`s: +Next we can see the initialization of the `memblock_type memory`, `memblock_type reserved` and `memblock_type physmem` fields of the `memblock` structure. Here we are interested only in the `memblock_type.regions` initialization process. Note that every `memblock_type` field is initialized by an array of `memblock_region`s: ```C static struct memblock_region memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS] __initdata_memblock;