On Thu, Jun 01, 2017 at 11:58:31AM +0800, Anand Jain wrote: > > > > @@ -59,7 +59,7 @@ static struct list_head *zlib_alloc_workspace(void) > > > > workspacesize = max(zlib_deflate_workspacesize(MAX_WBITS, MAX_MEM_LEVEL), > > zlib_inflate_workspacesize()); > > - workspace->strm.workspace = vmalloc(workspacesize); > > + workspace->strm.workspace = kvmalloc(workspacesize, GFP_KERNEL); > > workspace->buf = kmalloc(PAGE_SIZE, GFP_KERNEL); > > Workspace->buf can be a kvmalloc as well as in lzo? or I don't know if > there was any purpose for not doing it for zlib. Zlib is fine with PAGE_SIZE. Lzo needs potentially more than a page, and kvmalloc does not fallback to vmalloc in that case: http://elixir.free-electrons.com/linux/v4.12-rc3/source/mm/util.c#L378 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
