aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMinchan Kim <minchan@kernel.org>2016-01-14 15:22:32 -0800
committerMister Oyster <oysterized@gmail.com>2017-04-13 12:32:18 +0200
commit6d22d73c07a0f2ffe706e88c302d52371ad29206 (patch)
tree1870d26e56941ec7aa402865cfe6263957833367 /include
parente6af82ad8a5599a783e9850aca8f1b32fc1f93f4 (diff)
UPSTREAM: zram: pass gfp from zcomp frontend to backend
(cherry picked from commit 75d8947a36d0c9aedd69118d1f14bf424005c7c2) 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>
Diffstat (limited to 'include')
-rw-r--r--include/linux/zcomp.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/zcomp.h b/include/linux/zcomp.h
index c59d1fca7..5fb9769a3 100644
--- a/include/linux/zcomp.h
+++ b/include/linux/zcomp.h
@@ -33,7 +33,7 @@ struct zcomp_backend {
int (*decompress)(const unsigned char *src, size_t src_len,
unsigned char *dst);
- void *(*create)(void);
+ void *(*create)(gfp_t flags);
void (*destroy)(void *private);
const char *name;