[Sorry to jump in that late] On Tue 20-11-12 10:02:45, David Rientjes wrote: > On Mon, 19 Nov 2012, Glauber Costa wrote: > > > >> In the case I outlined below, for backwards compatibility. What I > > >> actually mean is that memcg *currently* allows arbitrary notifications. > > >> One way to merge those, while moving to a saner 3-point notification, is > > >> to still allow the old writes and fit them in the closest bucket. > > >> > > > > > > Yeah, but I'm wondering why three is the right answer. > > > > > > > This is unrelated to what I am talking about. > > I am talking about pre-defined values with a specific event meaning (in > > his patchset, 3) vs arbitrary numbers valued in bytes. > > > > Right, and I don't see how you can map the memcg thresholds onto Anton's > scheme that heavily relies upon reclaim activity; what bucket does a > threshold of 48MB in a memcg with a limit of 64MB fit into? > Perhaps you have some formula in mind that would do this, but I don't > see how it works correctly without factoring in configuration options > (memory compaction), type of allocation (GFP_ATOMIC won't trigger > Anton's reclaim scheme like GFP_KERNEL), altered min_free_kbytes, etc. > > This begs the question of whether the new cgroup should be considered as a > replacement for memory thresholds within memcg in the first place; > certainly both can coexist just fine. Absolutely agreed. Yes those two things are inherently different. Information that "you have passed half of your limit" is something totally different than "you should slow down". Although I am not entirely sure what the first is one good for (to be honest), but I believe there are users out there. I do not think that mixing those two makes much sense. They have different usecases and until we have users for the thresholds one we should keep it. [...] Thanks -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
