[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAmzW4ORSVsS_iji3gAcvepFqd3wsq0bXnxYOqnrYPH5ePykzA@mail.gmail.com>
Date: Sat, 27 Feb 2016 02:02:36 +0900
From: Joonsoo Kim <js1304@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [PATCH v2 12/17] mm/slab: do not change cache size if debug
pagealloc isn't possible
2016-02-27 1:13 GMT+09:00 Christoph Lameter <cl@...ux.com>:
> On Fri, 26 Feb 2016, js1304@...il.com wrote:
>
>> We can fail to setup off slab in some conditions. Even in this case,
>> debug pagealloc increases cache size to PAGE_SIZE in advance and it is
>> waste because debug pagealloc cannot work for it when it isn't the off
>> slab. To improve this situation, this patch checks first that this cache
>> with increased size is suitable for off slab. It actually increases cache
>> size when it is suitable for off-slab, so possible waste is removed.
>
> Maybe add some explanations to the code? You tried to simplify it earlier
> and make it understandable. This makes it difficult to understand it.
There is some explanation above the changed stuff although it doesn't
appear in the patch. And, this patch doesn't change any condition for it.
What this patch does is checking if it is suitable for off slab cache
in advance.
Before this patch, it is checked after increasing size and if it isn't
suitable for off slab cache, it cannot be used for debug_pagealloc with
increased size.
Thanks.
Powered by blists - more mailing lists