From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [RFC PATCH 0/7] mm: Get rid of vmalloc_sync_(un)mappings() Date: Fri, 8 May 2020 23:36:09 +0200 Message-ID: <20200508213609.GU8135@suse.de> References: <20200508144043.13893-1-joro@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org To: Andy Lutomirski Cc: Joerg Roedel , X86 ML , "H. Peter Anvin" , Dave Hansen , Peter Zijlstra , "Rafael J. Wysocki" , Arnd Bergmann , Andrew Morton , Steven Rostedt , Vlastimil Babka , Michal Hocko , LKML , Linux ACPI , linux-arch , Linux-MM List-Id: linux-arch.vger.kernel.org On Fri, May 08, 2020 at 02:33:19PM -0700, Andy Lutomirski wrote: > On Fri, May 8, 2020 at 7:40 AM Joerg Roedel wrote: > What's the maximum on other system types? It might make more sense to > take the memory hit and pre-populate all the tables at boot so we > never have to sync them. Need to look it up for 5-level paging, with 4-level paging its 64 pages to pre-populate the vmalloc area. But that would not solve the problem on x86-32, which needs to synchronize unmappings on the PMD level. Joerg From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 8 May 2020 23:36:09 +0200 From: Joerg Roedel Subject: Re: [RFC PATCH 0/7] mm: Get rid of vmalloc_sync_(un)mappings() Message-ID: <20200508213609.GU8135@suse.de> References: <20200508144043.13893-1-joro@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Andy Lutomirski Cc: Joerg Roedel , X86 ML , "H. Peter Anvin" , Dave Hansen , Peter Zijlstra , "Rafael J. Wysocki" , Arnd Bergmann , Andrew Morton , Steven Rostedt , Vlastimil Babka , Michal Hocko , LKML , Linux ACPI , linux-arch , Linux-MM List-ID: Message-ID: <20200508213609.86P8Q342Hi4tPy-jFyrCd5CCzElJBdsW0yFogJY18yk@z> On Fri, May 08, 2020 at 02:33:19PM -0700, Andy Lutomirski wrote: > On Fri, May 8, 2020 at 7:40 AM Joerg Roedel wrote: > What's the maximum on other system types? It might make more sense to > take the memory hit and pre-populate all the tables at boot so we > never have to sync them. Need to look it up for 5-level paging, with 4-level paging its 64 pages to pre-populate the vmalloc area. But that would not solve the problem on x86-32, which needs to synchronize unmappings on the PMD level. Joerg