Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754081AbbKYOwI (ORCPT ); Wed, 25 Nov 2015 09:52:08 -0500 Received: from mail-wm0-f46.google.com ([74.125.82.46]:37725 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753986AbbKYOwE (ORCPT ); Wed, 25 Nov 2015 09:52:04 -0500 Date: Wed, 25 Nov 2015 15:52:02 +0100 From: Michal Hocko To: Vlastimil Babka Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Joonsoo Kim , Minchan Kim , Sasha Levin , "Kirill A. Shutemov" , Mel Gorman Subject: Re: [PATCH v2 3/9] mm, page_owner: convert page_owner_inited to static key Message-ID: <20151125145202.GL27283@dhcp22.suse.cz> References: <1448368581-6923-1-git-send-email-vbabka@suse.cz> <1448368581-6923-4-git-send-email-vbabka@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448368581-6923-4-git-send-email-vbabka@suse.cz> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 765 Lines: 17 On Tue 24-11-15 13:36:15, Vlastimil Babka wrote: > CONFIG_PAGE_OWNER attempts to impose negligible runtime overhead when enabled > during compilation, but not actually enabled during runtime by boot param > page_owner=on. This overhead can be further reduced using the static key > mechanism, which this patch does. Is this really worth doing? If we do not have jump labels then the check will be atomic rather than a simple access, so it would be more costly, no? Or am I missing something? -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/