From 88857ecc7f15dd8471b5ddd100c5255f13bd9360 Mon Sep 17 00:00:00 2001 From: texhno Date: Wed, 14 Feb 2024 02:30:56 +0000 Subject: [PATCH] Update Utility containers --- Utility-containers.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Utility-containers.md b/Utility-containers.md index 572ef42..d037f4c 100644 --- a/Utility-containers.md +++ b/Utility-containers.md @@ -3,8 +3,6 @@ (Add a section for each new utility container, as well as documentation) -A few dilemmas had already emerged before even having started writing any code. - ***Should the kernel be 32-bit or 64-bit?*** * 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.