|
On Tue, 29 Oct 2002, Hans Boldt wrote: > others. But since all processes in an SLS architecture share the > same (humongous) virtual address space, you need some means of > ensuring that a process really is allowed to access a particular > region of store. That puts more overhead on securing memory > accesses, which requires substantial capabilities in the CPU itself. > It also meant 16 byte pointers, which can increase memory > requirements. If you remember back to the early days of the S/38, it > had significant performance problems, which adversely affected the > way system programming was done. (There *were* some very good In addition to this it seems to me that there is another performance problem with single level store. I don't know this for sure but it seems right. If an object in main memory needs to be pushed back to disk because memory is low, it is written back to its original location on disk. Then when it is retrieved back into main memory it is read again from that spot on the disk. This is ineffecient use of disk, as these reads/writes will be all over the place instead of in a closely clustered area of disk. James Rich
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.