Virtual memory size depends on
[a] address lines
[b] data bus
[c] disc space
[d] a & c [e] none

• virtual memory size depends on size of the address bus
  
• 7 years agoHelpfull: Yes(5) No(1)
• address lines
• 6 years agoHelpfull: Yes(2) No(0)
• A
  depends on Address bus(ie how much memory processor can access)
• 6 years agoHelpfull: Yes(1) No(0)
• The book seems to assume (incorrectly) that you won't allocate virtual memory that you don't plan to use. So, it warns that the physical memory and hard disk used for swap limit the usable virtual memory (of course, from the perspective of your process, so do the other demands on that resource pool - the OS and other processes).
  
  In practice, it's often useful to allocate more virtual memory than you could actually use, because you may want to, for example:
  
  use virtual memory for a sparse array, where you directly index in to a few scattered addresses,
  let the page faulting fail when the system resources actually run out, rather that complicating your code with some attempt to track available memory (remember this is dynamic with other processes etc.) or a pessimistic limit that means you fail to aggressively utilise your system capabilities
  let every program enjoy the benefits of believing it's been loaded at the address it was compiled for, so it can use absolute address for jump instructions etc.
• 7 years agoHelpfull: Yes(0) No(2)
• Address Lines (a)
• 7 years agoHelpfull: Yes(0) No(0)
• address line
• 6 years agoHelpfull: Yes(0) No(0)
• it depends upon size of address bus
• 6 years agoHelpfull: Yes(0) No(0)
• my answer is A
• 6 years agoHelpfull: Yes(0) No(0)
• option A Address bus
• 5 years agoHelpfull: Yes(0) No(0)
• address bus
• 5 years agoHelpfull: Yes(0) No(0)