Content deleted Content added
→'File slack' and 'slack space': new section |
AFBorchert (talk | contribs) |
||
Line 46:
“It ''(external fragmentation)'' is a weakness of certain storage allocation algorithms, when they fail to order memory used by programs efficiently” – surely it is a weakness of all general purpose algorithms, and any that fails to adequately anticipate sequence of (de)allocation operations? If so, this should be changed – or am I missing something? [[User:PJTraill|PJTraill]] ([[User talk:PJTraill|talk]]) 10:35, 4 November 2017 (UTC)
: One approach to avoid external fragmentation is to move surviving objects such that they are stored contiguously in memory. This is possible only for programming languages where each pointer is well-defined and where all pointers can found. Then this could be done using a garbage collector that is free to move objects. Alternatively, you can work with allocations of fixed memory units where objects are not necessarily stored contiguously in memory (see [https://dl.acm.org/doi/pdf/10.1145/354880.354883]). This, however, requires compiler support. --[[User:AFBorchert|AFBorchert]] ([[User talk:AFBorchert|talk]]) 11:33, 17 December 2020 (UTC)
== 'File slack' and 'slack space' ==
| |||