On Fri, Sep 18, 2015 at 4:03 AM, Vitaly Wool <vitalywool@xxxxxxxxx> wrote: >> I don't know how zsmalloc handles uncompressible PAGE_SIZE allocations, but >> I wouldn't expect it to be any more clever than this? So why duplicate the >> functionality in zswap and zbud? This could be handled e.g. at the zpool >> level? Or maybe just in zram, as IIRC in zswap (frontswap) it's valid just >> to reject a page and it goes to physical swap. zpool doesn't actually store pages anywhere; zbud and zsmalloc do the storing, and they do it in completely different ways. Storing an uncompressed page has to be done in zbud and zsmalloc, not zpool. And zram can't do it either; zram doesn't actually store pages either, it relies on zsmalloc to store all its pages. > > From what I can see, zsmalloc just allocates pages and puts them into > a linked list. Using the beginning of a page for storing an internal > struct is zbud-specific, and so is this patch. zsmalloc has size "classes" that allow storing "objects" of a specific size range (i.e. the last class size + 1, up to class size). the max size class is: #define ZS_MAX_ALLOC_SIZE PAGE_SIZE so zsmalloc is able to store "objects" up to, and including, PAGE_SIZE. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>