diff options
| author | Minchan Kim <minchan@kernel.org> | 2016-01-14 15:22:32 -0800 |
|---|---|---|
| committer | Mister Oyster <oysterized@gmail.com> | 2017-09-25 20:43:56 +0200 |
| commit | c5dae3b42cd3d9430115718eb97f8a32f84d0bb0 (patch) | |
| tree | 0ef6b3f804013714bb9734342e7c4a6b957ada1b /include/linux/unaligned | |
| parent | a60cd26f820ed18771601b27a7cd8a4c7cccf1f5 (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.
[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/linux/unaligned')
0 files changed, 0 insertions, 0 deletions