Also, you can use mlockall(MCL_CURRENT|MCL_FUTURE) and your malloc()
will actually get the pages immediately.
//Jesse Off
--- In Christopher Friedt <>
wrote:
>
> Likely, yes.
>
> The funny thing about linux (if you check man malloc) is that there
is
> no gaurantee that malloc'd memory is actually there. To quote the
author
> of the man page "this is a really bad bug".
>
> You can switch off the 'overcommit' bug by doing
>
> # echo 2 > /proc/sys/vm/overcommit_memory
>
> I would imagine that makes malloc return a gauranteed section of
memory.
>
> Does this relate somehow as well to linux killing random processes
when
> it runs low on memory?
>
> ~/Chris
>
> Yan Seiner wrote:
> > I've been trying to parse a large-ish XML file, and occasionally
I get:
> >
> > user.notice kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d0/0)
> >
> > ISTR that this somewhat cryptic error means the system is out of
memory.
> >
> > Is that right?
> >
> > --Yan
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|