From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f72.google.com (mail-wm0-f72.google.com [74.125.82.72]) by kanga.kvack.org (Postfix) with ESMTP id 0B68E6B000E for ; Wed, 14 Mar 2018 13:02:34 -0400 (EDT) Received: by mail-wm0-f72.google.com with SMTP id d23so1283317wmd.1 for ; Wed, 14 Mar 2018 10:02:33 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id b9sor1460778wrh.54.2018.03.14.10.02.32 for (Google Transport Security); Wed, 14 Mar 2018 10:02:32 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180314084329.y7735ecw2is5i5pd@esperanza> References: <20180313165428.58699-1-shakeelb@google.com> <20180314084329.y7735ecw2is5i5pd@esperanza> From: Shakeel Butt Date: Wed, 14 Mar 2018 10:02:30 -0700 Message-ID: Subject: Re: [PATCH] slab, slub: remove size disparity on debug kernel Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Vladimir Davydov Cc: Christopher Lameter , Suleiman Souhlal , Greg Thelen , Andrew Morton , Pekka Enberg , David Rientjes , Joonsoo Kim , Linux MM , LKML On Wed, Mar 14, 2018 at 1:43 AM, Vladimir Davydov wrote: > On Tue, Mar 13, 2018 at 10:36:52AM -0700, Shakeel Butt wrote: >> On Tue, Mar 13, 2018 at 10:19 AM, Christopher Lameter wrote: >> > On Tue, 13 Mar 2018, Shakeel Butt wrote: >> > >> >> However for SLUB in debug kernel, the sizes were same. On further >> >> inspection it is found that SLUB always use kmem_cache.object_size to >> >> measure the kmem_cache.size while SLAB use the given kmem_cache.size. In >> >> the debug kernel the slab's size can be larger than its object_size. >> >> Thus in the creation of non-root slab, the SLAB uses the root's size as >> >> base to calculate the non-root slab's size and thus non-root slab's size >> >> can be larger than the root slab's size. For SLUB, the non-root slab's >> >> size is measured based on the root's object_size and thus the size will >> >> remain same for root and non-root slab. >> > >> > Note that the object_size and size may differ for SLUB based on kernel >> > parameters and slab configuration. For SLAB these are compilation options. >> > >> >> Thanks for the explanation. >> >> >> @@ -379,7 +379,7 @@ struct kmem_cache *find_mergeable(unsigned int size, unsigned int align, >> >> } >> >> >> >> static struct kmem_cache *create_cache(const char *name, >> >> - unsigned int object_size, unsigned int size, unsigned int align, >> >> + unsigned int object_size, unsigned int align, >> >> slab_flags_t flags, unsigned int useroffset, >> > >> > Why was both the size and object_size passed during cache creation in the >> > first place? From the flags etc the slab logic should be able to compute >> > the actual bytes required for each object and its metadata. >> > >> >> +Vladimir >> >> I think it was introduced by 794b1248be4e7 ("memcg, slab: separate >> memcg vs root cache creation paths") but I could not find out the >> reason. > > This was a mistake - I missed that __kmem_cache_create() overwrites > kmem_cache->size. Thanks for fixing this. Thanks for confirming. Andrew, can you please add following line to the patch commit message. Fixes: 794b1248be4e ("memcg, slab: separate memcg vs root cache creation paths")