On Mon, May 30, 2016 at 09:53:25AM +0200, Dmitry Vyukov wrote: >On Mon, May 30, 2016 at 4:17 AM, kernel test robot > wrote: >> >> FYI, we noticed boot-slabinfo.num_objs +31.9% increasement due to commit: >> >> commit 55834c59098d0c5a97b0f3247e55832b67facdcf ("mm: kasan: initial memory quarantine implementation") >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master >> >> in testcase: boot >> on test machine: vm-lkp-wsx03-2G: 2 threads qemu-system-x86_64 -enable-kvm -cpu host with 2G memory >> with following parameters: sleep=1 >> >> >> Details are as below: >> --------------------------------------------------------------------------------------------------> >> >> >> ========================================================================================= >> compiler/kconfig/rootfs/sleep/tbox_group/testcase: >> gcc-6/x86_64-randconfig-s4-05280557/debian-x86_64-2015-02-07.cgz/1/vm-lkp-wsx03-2G/boot >> >> commit: >> b8f1a75d61d8405a753380c6fb17ba84a5603cd4 >> 55834c59098d0c5a97b0f3247e55832b67facdcf >> >> b8f1a75d61d8405a 55834c59098d0c5a97b0f3247e >> ---------------- -------------------------- >> %stddev %change %stddev >> \ | \ >> 165450 ± 0% +31.9% 218176 ± 1% boot-slabinfo.num_objs >> 19095 ± 5% +104.3% 39013 ± 3% boot-slabinfo.num_pages >> 107.27 ± 2% +14.1% 122.43 ± 13% boot-time.boot >> 97.13 ± 1% +4.3% 101.31 ± 1% boot-time.idle >> 1105076 ± 0% -7.2% 1025056 ± 0% boot-meminfo.MemFree >> 36269 ± 12% +215.7% 114517 ± 5% boot-meminfo.SUnreclaim >> 76469 ± 5% +104.5% 156343 ± 4% boot-meminfo.Slab >> >> >> >> boot-slabinfo.num_objs >> >> 230000 ++-----------------------------------------------------------------+ >> | O O | >> 220000 ++O O O OO OO O O OO OO | >> OO O OOOO O OOOOOOO O O OO O | >> 210000 ++ | >> | | >> 200000 ++ | >> | | >> 190000 ++ | >> | | >> 180000 ++ | >> | | >> 170000 ++ | >> ******************************************************************** >> 160000 ++-----------------------------------------------------------------+ >> >> >> boot-slabinfo.num_pages >> >> 45000 ++-------------O----------------------------------------------------+ >> | O O OO O O O O OOO | >> 40000 +O OOO OO OO O O | >> O OO O O O O O OO O O | >> | O O O | >> 35000 ++ | >> | | >> 30000 ++ | >> | | >> 25000 ++ | >> | | >> | * * * >> 20000 +* * * ** * * * * * * ** **** ** * * * * * * :: * *** *| >> * * ** ** * * ** *** * ** *** * * * * * ** *** * ** ** ** * * | >> 15000 ++------------------------------------------------------------------+ >> >> >> [*] bisect-good sample >> [O] bisect-bad sample > > >Hi Xiaolong, > >It is with CONFIG_KASAN=y? If yes, then increased memory usage is expected. Hi, Dmitry Yes, CONFIG_KASAN=y is set in config, see attached config file used for test. # CONFIG_KMEMCHECK is not set CONFIG_HAVE_ARCH_KASAN=y CONFIG_KASAN=y CONFIG_KASAN_OUTLINE=y # CONFIG_KASAN_INLINE is not set Thanks, Xiaolong