From: Balbir Singh on 1 Apr 2010 01:00 * KAMEZAWA Hiroyuki <kamezawa.hiroyu(a)jp.fujitsu.com> [2010-04-01 10:48:59]: > On Wed, 31 Mar 2010 13:57:46 -0400 > Rik van Riel <riel(a)redhat.com> wrote: > > > On 03/31/2010 11:54 AM, Larry Woodman wrote: > > > On Wed, 2010-03-31 at 11:28 -0400, Larry Woodman wrote: > > >> We are considering removing this printk at boot time from RHEL because > > >> it will confuse customers, encourage them to change the boot parameters > > >> and generate extraneous support calls. Its documented in > > >> Documentation/kernel-parameters.txt anyway. Any thoughts??? > > > > Yeah, that is a strange boot message... > > > > Acked-by: Rik van Riel <riel(a)redhat.com> > > > please CC linux-mm and maintainers. > > Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu(a)jp.fujitsu.com> > > It have been there for a year and I think memory usage by page_cgroup > will not surprise linux kernel users, more. > > Assume x86-32. > > RHEL allows amount of memory up to 16G, right? > > without memcg: memmap uses 32bytes * 16G/4k = 128M. > with memcg: memmap+page_cgroup uses (32+20) bytes * 16G/4k = 208M. > > I thought this may cause OOM in ZONE_NORMAL. Then, I added it when I wrote > original patch. This kind of memory eater can cause trouble when it pops > up suddenly. But I think 'one year' can be an excuse. > I've seen this issue come up on multiple machines, I think the printk is useful. However, we might need to change the panic() to a big fat warning and disable the memcg controller if we fail to allocate memory in page_cgroup_init_flatmem(). -- Three Cheers, Balbir -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [Question] race condition in mm/page_alloc.c regarding page->lru? Next: [ANNOUNCE] Git 1.7.0.4 |