Re: [PATCH v6 1/5] mm/sparse: abstract sparse buffer allocations

On Mon, Jul 16, 2018 at 01:44:43PM -0400, Pavel Tatashin wrote: > When struct pages are allocated for sparse-vmemmap VA layout, we first try > to allocate one large buffer, and than if that fails allocate struct pages > for each section as we go. > > The code that allocates buffer is uses global

Re: [PATCH v6 1/5] mm/sparse: abstract sparse buffer allocations

On Mon, Jul 16, 2018 at 01:44:43PM -0400, Pavel Tatashin wrote: > When struct pages are allocated for sparse-vmemmap VA layout, we first try > to allocate one large buffer, and than if that fails allocate struct pages > for each section as we go. > > The code that allocates buffer is uses global

[PATCH v6 1/5] mm/sparse: abstract sparse buffer allocations

When struct pages are allocated for sparse-vmemmap VA layout, we first try to allocate one large buffer, and than if that fails allocate struct pages for each section as we go. The code that allocates buffer is uses global variables and is spread across several call sites. Cleanup the code by

[PATCH v6 1/5] mm/sparse: abstract sparse buffer allocations

When struct pages are allocated for sparse-vmemmap VA layout, we first try to allocate one large buffer, and than if that fails allocate struct pages for each section as we go. The code that allocates buffer is uses global variables and is spread across several call sites. Cleanup the code by