vault backup: 2025-05-02 18:57:49
This commit is contained in:
@ -6,7 +6,7 @@ backlinks:
|
||||
- "[[Overview#Multitasking/Timesharing]]"
|
||||
---
|
||||
|
||||

|
||||

|
||||
|
||||
(C.U. - Control Unit, does FDE and communicates with everything like ALU, registers, etc.)
|
||||
|
||||
@ -47,26 +47,27 @@ The first solution for memory management is segmentation.
|
||||
|
||||
### Fragmentation
|
||||
- Each process requires a contiguous block
|
||||
|
||||
> [!caution] But fragmentation bad!
|
||||
> It happens when the free space of the main memory is divided up into multiple parts **between** processes. It's pretty clear why that's bad.
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||

|
||||
### Memory Allocation Algorithms
|
||||
Define which free segment should be allocated to a new process.
|
||||
|
||||
#### Best Fit
|
||||

|
||||

|
||||
|
||||
#### Worst fit
|
||||

|
||||

|
||||
|
||||
#### First fit
|
||||

|
||||

|
||||
|
||||
#### Compaction
|
||||

|
||||

|
||||
|
||||
|
||||
>[!warning]- Issues with this
|
||||
@ -77,7 +78,7 @@ Define which free segment should be allocated to a new process.
|
||||
## Direct Memory Access (DMA)
|
||||
In order to let CPU execute process instructions while data is being transferred from disk to memory, direct memory access (DMA) is used.
|
||||
|
||||

|
||||

|
||||
|
||||
## Fix-sized memory blocks
|
||||
In this scheme, memory is partitioned into blocks of the same size. Every block has the same number of bytes, which makes it easier for the system to keep track of which portions of memory are allocated or available.
|
||||
|
Reference in New Issue
Block a user