From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752465Ab3AWVpi (ORCPT ); Wed, 23 Jan 2013 16:45:38 -0500 Received: from mail-oa0-f50.google.com ([209.85.219.50]:58000 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752154Ab3AWVpd (ORCPT ); Wed, 23 Jan 2013 16:45:33 -0500 MIME-Version: 1.0 In-Reply-To: <20130123131713.GG13304@suse.de> References: <1358874762-19717-1-git-send-email-mgorman@suse.de> <1358874762-19717-6-git-send-email-mgorman@suse.de> <20130122144659.d512e05c.akpm@linux-foundation.org> <20130123131713.GG13304@suse.de> From: KOSAKI Motohiro Date: Wed, 23 Jan 2013 16:45:12 -0500 Message-ID: Subject: Re: [PATCH 5/6] mm: Fold page->_last_nid into page->flags where possible To: Mel Gorman Cc: Andrew Morton , Peter Zijlstra , Andrea Arcangeli , Ingo Molnar , Simon Jeons , Wanpeng Li , Hugh Dickins , Linux-MM , LKML Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Good question. > > There are 19 free bits in my configuration but it's related to > CONFIG_NODES_SHIFT which is 9 for me (512 nodes) and very heavily affected > by options such as CONFIG_SPARSEMEM_VMEMMAP. Memory hot-remove does not work > with CONFIG_SPARSEMEM_VMEMMAP and enterprise distribution configs may be > taking the performance hit to enable memory hot-remove. If I disable this > option to enable memory hot-remove then there are 0 free bits in page->flags. FWIW, when using current mmotm, memory hot memory remove does work w/ CONFIG_SPARSEMEM_VMEMMAP. Recently Fujitsu changed. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx199.postini.com [74.125.245.199]) by kanga.kvack.org (Postfix) with SMTP id D8D2A6B0008 for ; Wed, 23 Jan 2013 16:45:33 -0500 (EST) Received: by mail-ob0-f178.google.com with SMTP id eh20so8889295obb.9 for ; Wed, 23 Jan 2013 13:45:33 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20130123131713.GG13304@suse.de> References: <1358874762-19717-1-git-send-email-mgorman@suse.de> <1358874762-19717-6-git-send-email-mgorman@suse.de> <20130122144659.d512e05c.akpm@linux-foundation.org> <20130123131713.GG13304@suse.de> From: KOSAKI Motohiro Date: Wed, 23 Jan 2013 16:45:12 -0500 Message-ID: Subject: Re: [PATCH 5/6] mm: Fold page->_last_nid into page->flags where possible Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Andrew Morton , Peter Zijlstra , Andrea Arcangeli , Ingo Molnar , Simon Jeons , Wanpeng Li , Hugh Dickins , Linux-MM , LKML > Good question. > > There are 19 free bits in my configuration but it's related to > CONFIG_NODES_SHIFT which is 9 for me (512 nodes) and very heavily affected > by options such as CONFIG_SPARSEMEM_VMEMMAP. Memory hot-remove does not work > with CONFIG_SPARSEMEM_VMEMMAP and enterprise distribution configs may be > taking the performance hit to enable memory hot-remove. If I disable this > option to enable memory hot-remove then there are 0 free bits in page->flags. FWIW, when using current mmotm, memory hot memory remove does work w/ CONFIG_SPARSEMEM_VMEMMAP. Recently Fujitsu changed. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org