On 4/11/07, David Kreuter <[EMAIL PROTECTED]> wrote:
I understood that. I don't understand why existing code paths that have been around for *A WHILE* would be considered effort by developers, unless it was horribly broken. Shudder. Or no longer in the architecture, unlikely as that may be.
Go and measure. Compare z/VM paging I/O with spool I/O and see that on the same disks and the same block size, paging does one to two orders of magnitude more. This actually is a problem, but for spooling and not for paging. As pointed out, most installations these days count paging space in volumes rather than cylinders. For those, using full volumes for paging is not a big deal. No doubt one could redesign z/VM and write all code from scratch. That might even address some of the known itches in z/VM. And it would introduce an entire new set of problems that we did not see before. But we can just call that "restrictions" and insist that the hardware changes or that people buy more from it. -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
