On 03/23/2012 10:12 PM, Zhouping Liu wrote: > > 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 (0, 1, 2), 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
pushed, thanks Liu, if has problems, please feel free to send further fixing patches. Regards, Wanlong Gao > > Signed-off-by: Zhouping Liu <[email protected]> > --- > runtest/mm | 2 + > testcases/kernel/mem/tunable/min_free_kbytes.c | 237 > ++++++++++++++++++++++++ > 2 files changed, 239 insertions(+), 0 deletions(-) > create mode 100644 testcases/kernel/mem/tunable/min_free_kbytes.c > > thanks caspar's suggestions, I updated the patch. > v1 -> v2: > 1) using sig_handler to control the check_monitor thread, > 2) moved tst_* funcs in child, > 3) catch the return value in eatup_mem(). ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
