Re: Question on the current behaviour of malloc () on Linux

On 12/22/05, Jesper Juhl <[email protected]> wrote:
> On 12/21/05, Jie Zhang <[email protected]> wrote:
> > Hi,
> >
> > I first asked this question on uClinux mailing list. My first question
> > is <http://mailman.uclinux.org/pipermail/uclinux-dev/2005-December/036042.html>.
> > Although I found this issue on uClinux, it's also can be demostrated
> > on Linux. This is a small program:
> >
> [snip memory hog]
> >
> > When I run it on my Linux notebook, it will be killed. I expect to see
> > it prints out   "fail".
> >
>
> You are seeing the effects of Linux overcommitting memory.
>
[snip]
>
> For more information read Documentation/vm/overcommit-accounting ,
> Documentation/sysctl/vm.txt & Documentation/filesystems/proc.txt
>
Thanks a lot! Your explaination is very detailed and easier to
understand than the doc for me.

Best Regards,
Jie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Question on the current behaviour of malloc () on Linux
    • From: Jie Zhang <[email protected]>
  • Re: Question on the current behaviour of malloc () on Linux
    • From: Jesper Juhl <[email protected]>

• Prev by Date: Re: [PATCH] fix race with preempt_enable()
• Next by Date: Re: 2.6.15-rc6: known regressions in the kernel Bugzilla
• Previous by thread: Re: Question on the current behaviour of malloc () on Linux
• Next by thread: Re: Question on the current behaviour of malloc () on Linux
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]