Re: [PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

> > Signed-off-by: Pavel Tatashin > > Looks good to me, and it will make the code much shorter/easier. > > Reviewed-by: Oscar Salvador > Thank you! Pave

Re: [PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

> > Signed-off-by: Pavel Tatashin > > Looks good to me, and it will make the code much shorter/easier. > > Reviewed-by: Oscar Salvador > Thank you! Pave

Re: [PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

On Thu, Jul 12, 2018 at 04:37:29PM -0400, Pavel Tatashin wrote: > sparse_init() requires to temporary allocate two large buffers: > usemap_map and map_map. Baoquan He has identified that these buffers are so > large that Linux is not bootable on small memory machines, such as a kdump > boot. The

Re: [PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

On Thu, Jul 12, 2018 at 04:37:29PM -0400, Pavel Tatashin wrote: > sparse_init() requires to temporary allocate two large buffers: > usemap_map and map_map. Baoquan He has identified that these buffers are so > large that Linux is not bootable on small memory machines, such as a kdump > boot. The

[PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

sparse_init() requires to temporary allocate two large buffers: usemap_map and map_map. Baoquan He has identified that these buffers are so large that Linux is not bootable on small memory machines, such as a kdump boot. The buffers are especially large when CONFIG_X86_5LEVEL is set, as they are

[PATCH v5 4/5] mm/sparse: add new sparse_init_nid() and sparse_init()

sparse_init() requires to temporary allocate two large buffers: usemap_map and map_map. Baoquan He has identified that these buffers are so large that Linux is not bootable on small memory machines, such as a kdump boot. The buffers are especially large when CONFIG_X86_5LEVEL is set, as they are