4 ms·
A well motivated exploration. The paper largely: 1. Lay the reasoning of direct physical memory programs. The primary argument is that the cumulated complexit
by justicezyx 6y ago
A well motivated exploration.
The paper largely:
1. Lay the reasoning of direct physical memory programs. The primary argument is that the cumulated complexity in chip and OS, for virtual memory is too large; and that limits the design scope and retards advancement (huge page is used as an example). Meanwhile, 5 major changes needed in OS and application programs to use physical memory directly were listed, which appears fairly straightforward (no doubt more complexity is hidden).
2. The paper then explored the performance penalty of supporting large continuous memory abstraction in such a new programming paradigm. They proposed 2 cases needed to support the abstraction: dynamic allocated stack, and tree-based array. Experiments are carried out to run modified program that addresses these 2 cases.
One thing I could not easily see is how their experiment rules out the existing virtual memory's impact to their modified programs, which are supposed to not need to use virtual memory.
- projektfu 6y agoProblems line up on memory fragmentation and dynamic allocation. Systems like Macintosh (before OS X) and Windows 1-3 handled this with an additional level of indirection (handles) and relocation/compaction. You could also do it with smarter code that explicitly tagged pointers so they could be updated when the data moved.