On Thu, Oct 07, 2010 at 04:01:02PM +0200, Laurent Pinchart wrote: > Do we have an infrastructure, or even an embryo thereof, to remove pages from > the kernel's direct-mapped memory mapping at runtime ? The use of super pages > probably complicates the matter. No, and yes, using section mappings/supersection mappings further complicates the issue because these are duplicated across all processes in the system. Even if you did walk all processes in the system, if your system is SMP without h/w TLB broadcasting, you'd need to IPI the other CPUs and wait for the IPI to complete - which you can not do if you're trying to allocate non-cacheable memory from IRQ context. We _could_ reduce TASK_SIZE to be slightly below 2GB, which then means we can split the page tables in hardware, but I don't think its safe to assume that the kernel will always use the init_mm page table to lookup the >2GB page table entries. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
