This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Use malloca instead alloca

From: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
To: Ondřej Bílka <neleai at seznam dot cz>
Cc: Paul Eggert <eggert at cs dot ucla dot edu>, bug-gnulib <bug-gnulib at gnu dot org>, libc-alpha <libc-alpha at sourceware dot org>
Date: Sun, 30 Dec 2012 12:38:40 -0500
Subject: Re: [PATCH] Use malloca instead alloca
References: <20121228132908.GA23510@domone> <50DDD217.4050707@cs.ucla.edu><20121228173823.GA15219@domone> <20121228201729.GD20323@brightrain.aerifal.cx><20121229103315.GA9680@domone> <50DF2A7C.3080906@cs.ucla.edu> <20121229191822.GA26211@domone>

> And on linux it will always succeed and be killed by oom later.

I suspect you forgot /proc/sys/vm/overcommit_memory=2 (i.e. account
always mode).
Moreover, the default mode (/proc/sys/vm/overcommit_memory=1, ie
account guess mode) also may return failure if you try obvious big
size allocation.

thank you.

References:
- [PATCH] Use malloca instead alloca
  - From: OndÅej BÃlka
- Re: [PATCH] Use malloca instead alloca
  - From: Paul Eggert
- Re: [PATCH] Use malloca instead alloca
  - From: OndÅej BÃlka
- Re: [PATCH] Use malloca instead alloca
  - From: Rich Felker
- Re: [PATCH] Use malloca instead alloca
  - From: OndÅej BÃlka
- Re: [PATCH] Use malloca instead alloca
  - From: Paul Eggert
- Re: [PATCH] Use malloca instead alloca
  - From: OndÅej BÃlka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]