From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx157.postini.com [74.125.245.157]) by kanga.kvack.org (Postfix) with SMTP id 421A86B002B for ; Fri, 28 Dec 2012 14:16:37 -0500 (EST) Received: by mail-bk0-f46.google.com with SMTP id q16so4791134bkw.5 for ; Fri, 28 Dec 2012 11:16:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1356293711-23864-1-git-send-email-sasha.levin@oracle.com> <1356293711-23864-2-git-send-email-sasha.levin@oracle.com> <50DCCE5A.4000805@oracle.com> <50DCD4CB.50205@oracle.com> Date: Fri, 28 Dec 2012 11:16:35 -0800 Message-ID: Subject: Re: [PATCH 2/3] mm, bootmem: panic in bootmem alloc functions even if slab is available From: Yinghai Lu Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: JoonSoo Kim Cc: Sasha Levin , David Rientjes , Andrew Morton , Johannes Weiner , "David S. Miller" , Tejun Heo , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Fri, Dec 28, 2012 at 6:42 AM, JoonSoo Kim wrote: > > I have a different idea. > How about removing fallback allocation in bootmem.c completely? > I don't know why it is there exactly. > But, warning for 'slab_is_available()' is there for a long time. > So, most people who misuse fallback allocation change their code adequately. > I think that removing fallback at this time is valid. Isn't it? if you guys really want to make thing simple, please do try to help to kill mm/bootmem.c and use memblock instead. at last we could the wrapper mm/nobootmem.c. Thanks Yinghai -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org