On this type of partitioned system where ppc64 runs, there is not much
administration that could be done to help the problem. As Anton
mentioned, when the system has been up for a long time, and memory has
been moving between partitions which support dynamic memory movement, it
is assured that memory will become very fragmented. As more partitions
on these systems become available, and resources migrate more freely,
the problem will get worse.
Whether this management from kernel to hardware addresses is done in the
hypervisor layer or the OS, the same overhead exists, given todays
hardware structure for PowerPC servers anyway. In todays ppc64
implementation, we just use an array to map from what the kernel sees as
its address space to what is put in the hardware page table and I/O
translation tables, thus not requiring any changes in independant code.
This does consume some storage, but the highly fragmented nature of our
platform memory drives this decision. I would like to see that data
structure decision left to the archs as different platform design points
may lead to different mapping decisions.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/