Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1741307
| From | "Kirill A. Shutemov" <kirill@shutemov.name> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHv7 01/19] mm/sparsemem: Allocate mem_section at runtime for SPARSEMEM_EXTREME |
| Date | 2017-09-28 11:10 +0200 |
| Message-ID | <uuCZs-743-11@gated-at.bofh.it> (permalink) |
| References | <ur1Wp-5gk-5@gated-at.bofh.it> <ur265-5yD-5@gated-at.bofh.it> <uuC3o-6tW-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Sep 28, 2017 at 10:07:11AM +0200, Ingo Molnar wrote: > > * Kirill A. Shutemov <kirill.shutemov@linux.intel.com> wrote: > > > Size of mem_section array depends on size of physical address space. > > > > In preparation for boot-time switching between paging modes on x86-64 > > we need to make allocation of mem_section dynamic. > > > > The patch allocates the array on the first call to > > sparse_memory_present_with_active_regions(). > > > > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> > > What is the size of the allocations here, in bytes, for the two main variants? For 4-level paging it's 32k. For 5-level paging it's 2M. -- Kirill A. Shutemov
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCHv7 01/19] mm/sparsemem: Allocate mem_section at runtime for SPARSEMEM_EXTREME Ingo Molnar <mingo@kernel.org> - 2017-09-28 10:10 +0200
Re: [PATCHv7 01/19] mm/sparsemem: Allocate mem_section at runtime for SPARSEMEM_EXTREME "Kirill A. Shutemov" <kirill@shutemov.name> - 2017-09-28 11:10 +0200
Re: [PATCHv7 01/19] mm/sparsemem: Allocate mem_section at runtime for SPARSEMEM_EXTREME Ingo Molnar <mingo@kernel.org> - 2017-09-28 11:50 +0200
csiph-web