Is there a special segment dedicated to dynamic memory in the memory of the process? C+++
-
If I understand it correctly, the glass is a predetermined piece of memory. Therefore, when new variables appear in the glass, they are recorded and counted quickly. What about the dynamic memory? Do I understand correctly that, at the level of the address area, a pile of no one has a single segment, and "whose" means all the other free address space that is available as necessary in the ranks? And it's not just a piece of remembrance for everything like glass, but only for a specific variable?
Or we have a memory page and all the variables that have been created with help when we're asking for memory.
newwrites and reads from there, and when the memory ends, is there another one?
-
If I understand it correctly, the glass is a predetermined piece of memory.
Somehow, it should be noted:
- In a multi-point annex, each flow has its own glass. Sometimes the size of these glasses needs to be adjusted;
- With the use of virtual memory, which is now most commonly used, the allocation of a piece of address space to an annex and the placing of a real memory by the LO on the page of this address area are different operations. In particular, if the size of the 100 mb is to be fixed, 100 mb of the address space will be allocated immediately and the actual 100 mb will be assigned to the annex not immediately but gradually.
And it's not just a piece of remembrance for everything like glass, but only for a specific variable?
Memory managers may have different algorithms. Usually, the manager has a free-page pool that already has an address space. Where possible, the new/malloc(s) provides memory from it, and delete/free(s) restores memory to it, but when the memory manager fails or loses, he requests additional address space from the LOs or returns surpluses.
Bullets may be several, for different sizes, to reduce fragmentation, or for different streams of a multi-point application, with a view to reducing kash interference and interlocks.
