sborovic/dmzOS
1
2
Fork 1
Code Issues 8 Pull Requests Packages Projects 4 Releases Wiki Activity

Update Utility containers

texhno 2024-02-14 02:30:56 +00:00
parent 417f767f2b
commit 88857ecc7f
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Utility-containers.md

@ -3,8 +3,6 @@
(Add a section for each new utility container, as well as documentation) (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?*** ***Should the kernel be 32-bit or 64-bit?***
* A 32-bit kernel can provide access to 2<sup>32</sup> memory addresses. For a byte-addressable memory, that equals 2<sup>32</sup> B = 4*2<sup>30</sup> B = 4 GiB of physical memory. On the other hand, a 64-bit kernel can provide access to 2<sup>64</sup> B = 16 EiB of physical memory. * A 32-bit kernel can provide access to 2<sup>32</sup> memory addresses. For a byte-addressable memory, that equals 2<sup>32</sup> B = 4*2<sup>30</sup> B = 4 GiB of physical memory. On the other hand, a 64-bit kernel can provide access to 2<sup>64</sup> 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. * 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.