From: Yinghai Lu <yinghai@kernel.org>
To: JoonSoo Kim <js1304@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"David S. Miller" <davem@davemloft.net>,
Tejun Heo <tj@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mm, bootmem: panic in bootmem alloc functions even if slab is available
Date: Fri, 28 Dec 2012 11:16:35 -0800 [thread overview]
Message-ID: <CAE9FiQVXsv1c1KAs7F6yeE_BS8Zg_s6qk8Hb0qgPFNCmEfz5gA@mail.gmail.com> (raw)
In-Reply-To: <CAAmzW4MhCyYkdpOaHnJtoMoJeFsXQJXN=Cpo3s67=s+id-hrMg@mail.gmail.com>
On Fri, Dec 28, 2012 at 6:42 AM, JoonSoo Kim <js1304@gmail.com> 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-12-28 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 20:15 [PATCH 1/3] mm, sparse: allocate bootmem without panicing in sparse_mem_maps_populate_node Sasha Levin
2012-12-23 20:15 ` [PATCH 2/3] mm, bootmem: panic in bootmem alloc functions even if slab is available Sasha Levin
2012-12-27 22:25 ` David Rientjes
2012-12-27 22:27 ` Pekka Enberg
2012-12-27 22:31 ` David Rientjes
2012-12-27 22:38 ` Pekka Enberg
2012-12-27 22:40 ` Sasha Levin
2012-12-27 23:04 ` David Rientjes
2012-12-27 23:07 ` Sasha Levin
2012-12-28 14:42 ` JoonSoo Kim
2012-12-28 19:16 ` Yinghai Lu [this message]
2012-12-23 20:15 ` [PATCH 3/3] mm, sparse: don't check return value of alloc_bootmem calls Sasha Levin
2012-12-27 22:28 ` David Rientjes
2012-12-27 22:23 ` [PATCH 1/3] mm, sparse: allocate bootmem without panicing in sparse_mem_maps_populate_node David Rientjes
2012-12-27 22:41 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE9FiQVXsv1c1KAs7F6yeE_BS8Zg_s6qk8Hb0qgPFNCmEfz5gA@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hannes@cmpxchg.org \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox