On Wed, May 16, 2012 at 03:30:23PM +0100, Matthew Garrett wrote: > On Wed, May 16, 2012 at 04:28:31PM +0200, Lennart Poettering wrote: > > > Mhmm, so I was under the impression that x32 was mostly about increasing > > the scalability of virtualized systems. i.e. run a higher number of > > x32 containers/VM on an x86_64 host. Most server software that is run in > > containers/VMs does not require 64bit address space, and hence using x32 > > for them should be quite benificial so that you can run more > > containers/VMs per host. After all this would reduce memory and CPU > > consumption of each, and due to smaller memory usage also result in less > > IO? > > I was under the impression that it was to make Android work better on > Intel. Scalable VMs are an interesting idea, but for a typical session > how much RAM are we talking about? ... and also how does it compare to other (better IMHO) approaches such as KSM? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
