linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jie Zhang <jzhang918@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, lars.friedrich@wago.com
Subject: Re: Question on the current behaviour of malloc () on Linux
Date: Thu, 22 Dec 2005 15:15:43 +0800	[thread overview]
Message-ID: <6f48278f0512212315n24301308ia81fc8094fc93838@mail.gmail.com> (raw)
In-Reply-To: <9a8748490512211005u40ca4c7dv41044827544f97fa@mail.gmail.com>

On 12/22/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 12/21/05, Jie Zhang <jzhang918@gmail.com> 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

  parent reply	other threads:[~2005-12-22  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 17:36 Question on the current behaviour of malloc () on Linux Jie Zhang
2005-12-21 17:39 ` Arjan van de Ven
2005-12-21 18:05 ` Jesper Juhl
2005-12-21 18:07   ` Jesper Juhl
2005-12-22  7:15   ` Jie Zhang [this message]
2005-12-21 18:06 ` linux-os (Dick Johnson)
2005-12-21 19:00   ` Jesper Juhl
2005-12-22  7:21   ` Jie Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6f48278f0512212315n24301308ia81fc8094fc93838@mail.gmail.com \
    --to=jzhang918@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=lars.friedrich@wago.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).