From: Rik van Riel <riel@redhat.com>
To: gaoqiang <gaoqiangscut@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: bug for stack ?
Date: Wed, 18 Apr 2012 11:52:58 -0400 [thread overview]
Message-ID: <4F8EE35A.3060200@redhat.com> (raw)
In-Reply-To: <op.wcwj76p5n27o5l@gaoqiang-d1.corp.qihoo.net>
On 04/17/2012 05:20 AM, gaoqiang wrote:
>
> memory allocated for process stack seems never to be freed by the kernel..
It should get freed on process exit.
> on a vmware machine with about 768m memory, run the following program.when
> printing "run over", run another case of the following program. oom-killer
> trigered, which is not so reasonable.
You start your second run before your first run
has exited. The system does not have enough
memory for two such runs, so you run out of
memory.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-04-18 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 9:20 bug for stack ? gaoqiang
2012-04-18 15:52 ` Rik van Riel [this message]
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=4F8EE35A.3060200@redhat.com \
--to=riel@redhat.com \
--cc=gaoqiangscut@gmail.com \
--cc=linux-mm@kvack.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).