summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMinchan Kim <minchan@kernel.org>2016-01-15 02:22:32 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2016-01-15 22:40:51 +0300
commit75d8947a36d0c9aedd69118d1f14bf424005c7c2 (patch)
tree2fb49d36e4db0591ebd3fe42101379f9aa9b9c90 /README
parentd913897abace843bba20249f3190167f7895e9c3 (diff)
downloadlinux-75d8947a36d0c9aedd69118d1f14bf424005c7c2.tar.xz
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 'README')
0 files changed, 0 insertions, 0 deletions