[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160427123751.GI2858@techsingularity.net>
Date: Wed, 27 Apr 2016 13:37:51 +0100
From: Mel Gorman <mgorman@...hsingularity.net>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Jesper Dangaard Brouer <brouer@...hat.com>
Subject: Re: [PATCH 1/3] mm, page_alloc: un-inline the bad part of
free_pages_check
On Wed, Apr 27, 2016 at 02:01:14PM +0200, Vlastimil Babka wrote:
> !DEBUG_VM bloat-o-meter:
>
> add/remove: 1/0 grow/shrink: 0/2 up/down: 124/-383 (-259)
> function old new delta
> free_pages_check_bad - 124 +124
> free_pcppages_bulk 1509 1403 -106
> __free_pages_ok 1025 748 -277
>
> DEBUG_VM:
>
> add/remove: 1/0 grow/shrink: 0/1 up/down: 124/-242 (-118)
> function old new delta
> free_pages_check_bad - 124 +124
> free_pages_prepare 1048 806 -242
>
> Signed-off-by: Vlastimil Babka <vbabka@...e.cz>
This uninlines the check all right but it also introduces new function
calls into the free path. As it's the free fast path, I suspect it would
be a step in the wrong direction from a performance perspective.
--
Mel Gorman
SUSE Labs
Powered by blists - more mailing lists