This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Question about madvise(DONTNEED) in glibc malloc
- From: chrubis at suse dot cz
- To: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 18 Apr 2013 16:52:25 +0200
- Subject: Re: Question about madvise(DONTNEED) in glibc malloc
- References: <516ADB3C dot 9040805 at gmail dot com> <20130415042809 dot GT20323 at brightrain dot aerifal dot cx> <516B89C0 dot 7060904 at gmail dot com>
Hi!
> > If vrange can fail to "get back" the range,
> > this makes it a lot harder to use robustly.
>
> Any linux syscall _can_ return ENOMEM if system has really no memory.
> but we've never seen practically because kernel handle memory starvation enough
> clever.
Unless somebody has set ulimit for memory, you can actually see pretty
weird crashes and bugs in that case.
--
Cyril Hrubis
chrubis@suse.cz