Hello, Vladimir. On Mon, Sep 07, 2015 at 02:38:22PM +0300, Vladimir Davydov wrote: > > As long as kernel doesn't have a run-away allocation spree, this > > should provide enough protection while making kmemcg behave more > > consistently. > > Another good thing about such an approach is that it copes with prio > inversion. Currently, a task with small memory.high might issue > memory.high reclaim on kmem charge with a bunch of various locks held. > If a task with a big value of memory.high needs any of these locks, > it'll have to wait until the low prio task finishes reclaim and releases > the locks. By handing over reclaim to task_work whenever possible we > might avoid this issue and improve overall performance. Indeed, will update the patch accordingly. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
