Hi, On Thu, Jun 12, 2014 at 03:58:42PM +0900, Joonsoo Kim wrote: > On Fri, Jun 06, 2014 at 05:22:42PM +0400, Vladimir Davydov wrote: > > @@ -2673,18 +2673,11 @@ static __always_inline void slab_free(struct > > kmem_cache *s, > > > > slab_free_hook(s, x); > > > > -redo: > > - /* > > - * Determine the currently cpus per cpu slab. > > - * The cpu may change afterward. However that does not matter since > > - * data is retrieved via this pointer. If we are on the same cpu > > - * during the cmpxchg then the free will succedd. > > - */ > > preempt_disable(); > > Could you add some code comment why this preempt_disable/enable() is > needed? We don't have any clue that kmemcg depends on these things > on code, so someone cannot understand why it is here. > > If possible, please add similar code comment on slab_alloc in mm/slab.c.
Sure. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
