From: Sravan V Dodla <sravan@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] mem/tunable: fix the overcommitting possible failure
Date: Thu, 17 Jan 2013 12:37:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20130117T133157-543@post.gmane.org> (raw)
In-Reply-To: 4F4313F6.9020408@cn.fujitsu.com
Wanlong Gao <gaowanlong@...> writes:
>
> On 02/21/2012 11:43 AM, Wanlong Gao wrote:
>
> > 1. CommitLimit may be changed when set another overcommit_memory
> > value.
> > 2. Test overcommit_memory=2 first to avoid the condition
> > committed > CommitLimited.
>
> Below is my failure before this patch.
Some how even after the patch I still hit this issue.
Wanlong, is it good to skip this case of test when CommitLimit < Committed_AS.
Please comment.
./overcommit_memory -R 0
overcommit_memory 0 TINFO : set overcommit_ratio to 0
overcommit_memory 0 TINFO : MemTotal is 1020764 kB
overcommit_memory 0 TINFO : SwapTotal is 0 kB
overcommit_memory 0 TINFO : CommitLimit is 0 kB
overcommit_memory 0 TINFO : set overcommit_memory to 2
overcommit_memory 0 TINFO : CommmitLimit is 0, Committed_AS is 241680
overcommit_memory 1 TBROK : Unexpected error: CommitLimit < Committed_AS
overcommit_memory 2 TBROK : Remaining cases broken
overcommit_memory 0 TINFO : set overcommit_memory to 0
overcommit_memory 0 TINFO : set overcommit_ratio to 50
> ---
> # ./overcommit_memory -R 0 ; cat /proc/meminfo
> overcommit_memory 0 TINFO : set overcommit_ratio to 0
> overcommit_memory 0 TINFO : MemTotal is 5780068 kB
> overcommit_memory 0 TINFO : SwapTotal is 4095996 kB
> overcommit_memory 0 TINFO : CommitLimit is 4095996 kB
> overcommit_memory 0 TINFO : set overcommit_memory to 0
> overcommit_memory 0 TINFO : malloc 2127578 kB successfully
> overcommit_memory 1 TPASS : alloc passed as expected
> overcommit_memory 0 TINFO : malloc 8510312 kB failed
> overcommit_memory 2 TPASS : alloc failed as expected
> overcommit_memory 0 TINFO : malloc 9876064 kB failed
> overcommit_memory 3 TPASS : alloc failed as expected
> overcommit_memory 0 TINFO : set overcommit_memory to 2
> overcommit_memory 0 TINFO : CommmitLimit is 4095996, Committed_AS is
4096060
> overcommit_memory 4 TBROK : Unexpected error: CommitLimit < Committed_AS
> overcommit_memory 5 TBROK : Remaining cases broken
> overcommit_memory 0 TINFO : set overcommit_memory to 0
> overcommit_memory 0 TINFO : set overcommit_ratio to 50
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2013-01-17 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329795813-12550-1-git-send-email-gaowanlong@cn.fujitsu.com>
[not found] ` <4F4313F6.9020408@cn.fujitsu.com>
2013-01-17 12:37 ` Sravan V Dodla [this message]
2013-01-22 8:38 ` [LTP] [PATCH] mem/tunable: fix the overcommitting possible failure Wanlong Gao
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=loom.20130117T133157-543@post.gmane.org \
--to=sravan@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
/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