On Thu, Jan 22, 2015 at 11:27 PM, David Rientjes <[email protected]> wrote: > If you reset the hwm for a process, rss grows to 100MB, another process > resets the hwm, and you see a hwm of 2MB, that invalidates the hwm > entirely.
Not sure I follow this scenario. Where does the 2MB come from? How can you see a hwm of 2MB, under which conditions? HVM can never be < RSS. Again, what you are talking about is the case of two profilers racing for using the same interface (hwm). This is the same case today of the PG_referenced bit. > The hwm is already defined as the > highest rss the process has attained, resetting it and trying to make any > inference from the result is racy and invalidates the actual value which > is useful. The counter arugment is: once you have one very high peak, the hvm becomes essentially useless for the rest of the lifetime of the process (until a higher peak comes). This makes very hard to understand what is going on in the meanwhile (from userspace). Anyways, are you proposing to pursue a different approach? Is the approach 2. that petrcermark@ proposed in the beginning of the thread going to address this concern? -- 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/
