From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755446AbdCXClw (ORCPT ); Thu, 23 Mar 2017 22:41:52 -0400 Received: from mga06.intel.com ([134.134.136.31]:51789 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbdCXClu (ORCPT ); Thu, 23 Mar 2017 22:41:50 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,213,1486454400"; d="scan'208";a="947667151" From: "Huang\, Ying" To: David Rientjes Cc: "Huang\, Ying" , Andrew Morton , Andi Kleen , Dave Hansen , Shaohua Li , Rik van Riel , Tim Chen , Michal Hocko , Mel Gorman , Aaron Lu , Gerald Schaefer , "Kirill A. Shutemov" , Hugh Dickins , "Ingo Molnar" , Vegard Nossum , , Subject: Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure References: <20170320084732.3375-1-ying.huang@intel.com> Date: Fri, 24 Mar 2017 10:41:45 +0800 In-Reply-To: (David Rientjes's message of "Mon, 20 Mar 2017 14:32:27 -0700") Message-ID: <8737e3z992.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org David Rientjes writes: > On Mon, 20 Mar 2017, Huang, Ying wrote: > >> From: Huang Ying >> >> Now vzalloc() is used in swap code to allocate various data >> structures, such as swap cache, swap slots cache, cluster info, etc. >> Because the size may be too large on some system, so that normal >> kzalloc() may fail. But using kzalloc() has some advantages, for >> example, less memory fragmentation, less TLB pressure, etc. So change >> the data structure allocation in swap code to use kvzalloc() which >> will try kzalloc() firstly, and fallback to vzalloc() if kzalloc() >> failed. >> > > As questioned in -v1 of this patch, what is the benefit of directly > compacting and reclaiming memory for high-order pages by first preferring > kmalloc() if this does not require contiguous memory? The memory allocation here is only for swap on time, not for swap out/in time. The performance of swap on is not considered critical. But if the kmalloc() is used instead of the vmalloc(), the swap out/in performance could be improved (marginally). More importantly, the interference for the other activity on the system could be reduced, For example, less memory fragmentation, less TLB usage of swap subsystem, etc. Best Regards, Huang, Ying