>> Vmalloc may offen get pages by loop invoke alloc_pags, this is >> cost too much time in count watermark/cpuset or something. >> Let's just try alloc by alloc_pages_bulk, if failed, fullback in >> original path. >> >> With my own test, simulate loop alloc_page and alloc_pages_bulk_array, >> get this: >> size 1M 10M 20M 30 >> normal 44 1278 3665 5581 >> test 34 889 2167 3300 >> optimize 22% 30% 40% 40% >> And in my vmalloc top sort, zram/f2fs may alloc more than 20MB, so, >> It's worth to use alloc_pages_bulk. >> >> Signed-off-by: Yang Huan <link@xxxxxxxx> > >Thanks. I suggest you take a look at the current merge window and check >if anything additional needs to be done after the vmalloc bulk allocation Sorry for that, I will work in linux-next >by Uladzislau Rezki. > >-- >Mel Gorman >SUSE Labs Yang Huan
