From: ZhoupingLiu <zliu@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] mm/tunable: add a new testcase min_free_kbytes
Date: Fri, 23 Mar 2012 22:16:23 +0800 [thread overview]
Message-ID: <4F6C85B7.4040604@redhat.com> (raw)
In-Reply-To: <4F6B2A08.5070709@cn.fujitsu.com>
On 03/22/2012 09:32 PM, Wanlong Gao wrote:
> On 03/22/2012 02:35 PM, Zhouping Liu wrote:
>
>> The case is designed to test min_free_kbytes tunable file.
>>
>> The tune is used to control free memory, and system always
>> reserve min_free_kbytes memory at least.
>>
>> Since the tune is not too large or too little, which will
>> lead to the system hang, so I choose two cases, and test them
>> on all overcommit_memory policy, at the same time, compare
>> the current free memory with the tunable value repeatedly.
>>
>> a) default min_free_kbytes with all overcommit memory policy
>> b) half of mem_free with all overcommit memory policy
>
> Looks good and test OK to me. thanks,
>
> Reviewed-by: Wanlong Gao<gaowanlong@cn.fujitsu.com>
>
hi, Wanlong
Thanks for your reviewing :)
I sent a new version, please review it again.
Thanks,
Zhouping
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-03-23 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 6:35 [LTP] [PATCH] mm/tunable: add a new testcase min_free_kbytes Zhouping Liu
2012-03-22 13:32 ` Wanlong Gao
2012-03-23 14:16 ` ZhoupingLiu [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=4F6C85B7.4040604@redhat.com \
--to=zliu@redhat.com \
--cc=gaowanlong@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.