On Thu, 11 Feb 2010, Nick Bowler wrote: > > As mentioned in the changelog, we've exported these minimum and maximum > > values via a kernel header file since at least 2006. At what point do we > > assume they are going to be used and not hardcoded into applications? > > That was certainly the intention when making them user visible. > > The thing is, even when the macros are used, their values are hardcoded > into programs once the code is run through a compiler. That's why it's > called an ABI. > Right, that's the second point that I listed: since the semantics of the tunable have radically changed from the bitshift to an actual unit (proportion of available memory), those applications need to change how they use oom_adj anyway. The bitshift simply isn't extendable with any sane heuristic that is predictable or works with any reasonable amount of granularity, so this change seems inevitable in the long term. We may be forced to abandon /proc/pid/oom_adj itself and introduce the tunable with a different name: oom_score_adj, for example, to make it clear that it's a different entity. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>