diff options
| author | Minchan Kim <minchan@kernel.org> | 2016-01-14 15:22:32 -0800 |
|---|---|---|
| committer | Peter Kalauskas <peskal@google.com> | 2018-08-23 11:59:44 -0700 |
| commit | dc5f588d8b73b20e17b783c7ef25faef4130fcad (patch) | |
| tree | 60d96a27faf1d5c0d9aa7d6074281a86dd3d48ed /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 3a2ec581f8e1b2f2ea949d4de42b99945cac5972 (diff) | |
UPSTREAM: 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.
[sergey.senozhatsky@gmail.com: add missing __vmalloc zero and highmem gfps]
Signed-off-by: Minchan Kim <minchan@kernel.org>
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 75d8947a36d0c9aedd69118d1f14bf424005c7c2)
Signed-off-by: Peter Kalauskas <peskal@google.com>
Bug: 112488418
Change-Id: I572d0565de5aff94ebe0782eba9d34f9c9862060
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions