From 29c7f4c08576e73ff0cbcc056dc1acf09742dcab Mon Sep 17 00:00:00 2001 From: texhno Date: Wed, 14 Feb 2024 02:31:06 +0000 Subject: [PATCH] Update Utility containers --- Utility-containers.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/Utility-containers.md b/Utility-containers.md index a17cb15..e837992 100644 --- a/Utility-containers.md +++ b/Utility-containers.md @@ -2,10 +2,6 @@ (Add a section for each new utility container, as well as documentation) -* A 32-bit kernel can provide access to 232 memory addresses. For a byte-addressable memory, that equals 232 B = 4*230 B = 4 GiB of physical memory. On the other hand, a 64-bit kernel can provide access to 264 B = 16 EiB of physical memory. -* Having more RAM available makes heavy multitasking and memory-intensive operations perform better. On the other hand, 64-bit programs use about 50% more memory then their 32-bit counterpart; this is due to numerous reasons, one of which is that 64-bit pointers take up twice as much space as 32-bit ones. -* The x86_64 architecture has two primary [modes of operation](https://en.wikipedia.org/wiki/X86-64#Operating_modes), each having different sub-modes. A 64-bit and 32-bit kernel require the processor to operate in different modes. - *Decision*: In order to prevent running into chaos, we will first stick to the steps outlined in [Operating Systems: From 0 to 1][os01], which will result in our developing a 32-bit kernel stub. At that point, we will have necessary information to decide whether it aligns better with our goals to keep the kernel 32-bit or to convert it into a 64-bit version. ***Intel or AT&T syntax for asm code?***