{"title":"桌面上有很大的内存","authors":"J. Mogul","doi":"10.1109/WWOS.1993.348163","DOIUrl":null,"url":null,"abstract":"Operating systems people think of desktop systems as \"small\" machines and worry about supporting small main memories. This is a historical aberration; memory sizes (and memory demands) are growing faster than memory access times are decreasing, so desktop operating systems will have to do a better job at supporting large memories. I discuss three problem areas for programs with large address spaces: avoiding TLB misses, better use of backing store, and use of explicit control to avoid paging latencies.<<ETX>>","PeriodicalId":345070,"journal":{"name":"Proceedings of IEEE 4th Workshop on Workstation Operating Systems. WWOS-III","volume":"197 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-10-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"20","resultStr":"{\"title\":\"Big memories on the desktop\",\"authors\":\"J. Mogul\",\"doi\":\"10.1109/WWOS.1993.348163\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Operating systems people think of desktop systems as \\\"small\\\" machines and worry about supporting small main memories. This is a historical aberration; memory sizes (and memory demands) are growing faster than memory access times are decreasing, so desktop operating systems will have to do a better job at supporting large memories. I discuss three problem areas for programs with large address spaces: avoiding TLB misses, better use of backing store, and use of explicit control to avoid paging latencies.<<ETX>>\",\"PeriodicalId\":345070,\"journal\":{\"name\":\"Proceedings of IEEE 4th Workshop on Workstation Operating Systems. WWOS-III\",\"volume\":\"197 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-10-14\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"20\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of IEEE 4th Workshop on Workstation Operating Systems. WWOS-III\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/WWOS.1993.348163\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of IEEE 4th Workshop on Workstation Operating Systems. WWOS-III","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/WWOS.1993.348163","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Operating systems people think of desktop systems as "small" machines and worry about supporting small main memories. This is a historical aberration; memory sizes (and memory demands) are growing faster than memory access times are decreasing, so desktop operating systems will have to do a better job at supporting large memories. I discuss three problem areas for programs with large address spaces: avoiding TLB misses, better use of backing store, and use of explicit control to avoid paging latencies.<>