Ingo Molnar <[EMAIL PROTECTED]> wrote: > > app designers very frequently think that the VM gets its act wrong (most > of the time for the wrong reasons), and the last thing we want to enable > them is to hack real problems around.
Not really. Memory reclaim tries to predict the future and expects some sort of "average" workload. For some workloads that prediction is hopelessly wrong. Although we could surely provide manual hinting machinery which is less crude than this proposal. > . enable users to > specify an 'allocation priority' of some sort, which kicks out the > pagecache on the local node - or something like that. Yes, that would be preferable - I don't know what the difficulty is with that. sys_set_mempolicy() should provide a sufficiently good hint. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
