aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMinchan Kim <[email protected]>2016-01-14 15:22:32 -0800
committerLinus Torvalds <[email protected]>2016-01-15 11:40:51 -0800
commit75d8947a36d0c9aedd69118d1f14bf424005c7c2 (patch)
tree2fb49d36e4db0591ebd3fe42101379f9aa9b9c90 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentd913897abace843bba20249f3190167f7895e9c3 (diff)
zram: pass gfp from zcomp frontend to backend
Each zcomp backend uses own gfp flag but it's pointless because the context they could be called is driven by upper layer(ie, zcomp frontend). As well, zcomp frondend could call them in different context. One context(ie, zram init part) is it should be better to make sure successful allocation other context(ie, further stream allocation part for accelarating I/O speed) is just optional so let's pass gfp down from driver (ie, zcomp frontend) like normal MM convention. [[email protected]: add missing __vmalloc zero and highmem gfps] Signed-off-by: Minchan Kim <[email protected]> Signed-off-by: Sergey Senozhatsky <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions