On 05/04/2017 01:17 AM, Igor Stoppa wrote: > Or, let me put it differently: my goal is to not fracture more pages > than needed. > It will probably require some profiling to figure out what is the > ballpark of the memory footprint. This is easy to say, but hard to do. What if someone loads a different set of LSMs, or uses a very different configuration? How could this possibly work generally without vastly over-reserving in most cases? > I might have overlooked some aspect of this, but the overall goal > is to have a memory range (I won't call it zone, to avoid referring to a > specific implementation) which is as tightly packed as possible, stuffed > with all the data that is expected to become read-only. I'm starting with the assumption that a new zone isn't feasible. :) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
