aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMichal Hocko <[email protected]>2017-06-02 14:46:19 -0700
committerLinus Torvalds <[email protected]>2017-06-02 15:07:37 -0700
commit4f4f2ba9c531b3d7cee293dd3654ba3b86e7d220 (patch)
treee76d33e876e50dcbeb4dc88a919003657911b785 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent60b0a8c3d2480f3b57282b47b7cae7ee71c48635 (diff)
mm: clarify why we want kmalloc before falling backto vmallock
While converting drm_[cm]alloc* helpers to kvmalloc* variants Chris Wilson has wondered why we want to try kmalloc before vmalloc fallback even for larger allocations requests. Let's clarify that one larger physically contiguous block is less likely to fragment memory than many scattered pages which can prevent more large blocks from being created. [[email protected]: coding-style fixes] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Michal Hocko <[email protected]> Suggested-by: Chris Wilson <[email protected]> Reviewed-by: Chris Wilson <[email protected]> Acked-by: Vlastimil Babka <[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