R
Roger Levy
I'm interested in the basis of the twice guideline for ramdisks. After
populating the ramdisk with everything that would otherwise be on a physical
disk prior to boot, do the runtime processes copy "text" (program code) and
"constant data" into other RAM in the same way a disk based system would copy
them on demand from a physical disk? That would have been the most
straightforward implementation because it does not deal with the unique
properties of a ramdisk. A more efficient scheme would be to use text and
constant data directly from the ramdisk. At a minimum, this would require
contiguous files or at least files that appeared to be contiguous in a virtual
memory sense. I'm curious as to how it was implemented and whether using the
text in the virtual disk for execution was implemented or if it was considered
impractical.
Roger Levy
populating the ramdisk with everything that would otherwise be on a physical
disk prior to boot, do the runtime processes copy "text" (program code) and
"constant data" into other RAM in the same way a disk based system would copy
them on demand from a physical disk? That would have been the most
straightforward implementation because it does not deal with the unique
properties of a ramdisk. A more efficient scheme would be to use text and
constant data directly from the ramdisk. At a minimum, this would require
contiguous files or at least files that appeared to be contiguous in a virtual
memory sense. I'm curious as to how it was implemented and whether using the
text in the virtual disk for execution was implemented or if it was considered
impractical.
Roger Levy