Date: Sun, 30 Apr 2017 16:22:47 -0500 (CDT)
From: Christoph Lameter <cl@linux.com>
To: Wei Yang <richard.weiyang@gmail.com>
cc: penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
        akpm@linux-foundation.org, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] try to save some memory for kmem_cache in some
 cases
In-Reply-To: <20170430113152.6590-1-richard.weiyang@gmail.com>
Message-ID: <alpine.DEB.2.20.1704301621170.21370@east.gentwo.org>
References: <20170430113152.6590-1-richard.weiyang@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 531
Lines: 12

On Sun, 30 Apr 2017, Wei Yang wrote:

> kmem_cache is a frequently used data in kernel. During the code reading, I
> found maybe we could save some space in some cases.
>
> 1. On 64bit arch, type int will occupy a word if it doesn't sit well.
> 2. cpu_slab->partial is just used when CONFIG_SLUB_CPU_PARTIAL is set
> 3. cpu_partial is just used when CONFIG_SLUB_CPU_PARTIAL is set, while just
> save some space on 32bit arch.

This looks fine. But do we really want to add that amount of ifdeffery?
How much memory does this save?