From: Andrew Morton <firstname.lastname@example.org>
Date: Thu, 01 Aug 2002 17:37:46 -0700
Some observations which have been made thus far:
- Minimal impact on the VM and MM layers
Well the downside of this is that it means it isn't transparent
to userspace. For example, specfp2000 results aren't going to
improve after installing these changes. Some of the other large
page implementations would.
- The change to MAX_ORDER is unneeded
This is probably done to increase the likelyhood that 4MB page orders
are available. If we collapse 4MB pages deeper, they are less likely
to be broken up because smaller orders would be selected first.
Maybe it doesn't make a difference....
- swapping of large pages and making them pagecache-coherent is
Swapping them is easy, any time you hit a large PTE you unlarge it.
This is what some of other large page implementations do. Basically
the implementation is that set_pte() breaks apart large ptes when
I agree on the pagecache side.
Actually to be honest the other implementations seemed less
intrusive and easier to add support for. The downside is that
handling of weird cases like x86 using pmd's for 4MB pages
was not complete last time I checked.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:17 EST