摊位书上的家庭作业问题
a.为什么 vms/vax 进程状态中有这么多等待状态？
a.why is there so many wait states in the in the vms/vax process states ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
a.为什么 vms/vax 进程状态中有这么多等待状态？
a.why is there so many wait states in the in the vms/vax process states ?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（2）
除一项等待外，所有等待都与内存交换或线程交换有关。
VAX 架构具有虚拟寻址。一个程序最多可以访问 1 GB 的地址空间，这在 1977 年是巨大的。如果我没记错的话，32 或 64 MB 的内存是标准的。这意味着程序可以访问比机器实际拥有的内存更多的内存。 VAX 通过与磁盘驱动器之间的内存分页来管理虚拟内存。
多个用户可以使用 VAX。这是通过多个用户线程完成的。由于处理器一次只能执行一条指令，因此一次只能有一个线程处于活动状态。一般来说，线程会一直运行直到遇到 I/O 指令。当 I/O 指令完成时，该线程将被换出，并允许其他线程执行。
如果您想真正感受过去的感觉，请阅读特雷西·基德（Tracy Kidder）的《新机器的灵魂》。这是开发 Data General Eclipse MV/8000 团队的故事。
All of the waits except one have to do with memory swapping or thread swapping.
The VAX architecture had virtual addressing. A program could access up to 1 gigabyte of address space, which was huge in 1977. If I remember correctly, 32 or 64 megabytes of memory was the standard. This meant that programs could access more memory than the machine actually had. VAX managed this virtual memory by paging memory to and from a disk drive.
Multiple users could use the VAX. This was accomplished with multiple user threads. Since the processor could only execute one instruction at a time, only one thread could be active at a time. Generally, a thread would run until an I/O instruction was encountered. The thread would be swapped out, and other threads allowed to execute, while the I/O instruction completed.
If you want to really feel what it was like back in the olden days, read Tracy Kidder's "Soul of a New Machine". It's the story of the team that developed the Data General Eclipse MV/8000.
因为他们每个人都有自己的目的...
Because each one of them has its own purpose...