> This approach works on any task via it's proc, and can be used on different > tasks in parallel. > > Also, Andrew was asking for some performance numbers related to the change. > Now I can say, that as long as soft dirty bits are not cleared, no performance > penalty occur, since the soft dirty bit and the regular dirty bit are set at > the same time within the same instruction. When soft dirty is cleared via > clear_refs, the task in question might slow down, but it will depend on how > actively it uses the memory. > > > What do you think, does it make sense to develop this approach further?
When touching mmaped page, cpu turns on dirty bit but doesn't turn on soft dirty. So, I'm not convinced how to use this flag. Please show us your userland algorithm how to detect diff. -- 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/
