On (12/11/17 09:16), Minchan Kim wrote: [..] > I agree. zram shouldn't be aware of allocator internal. > It would be better for zram to use *int zs_max_zpage_size(struct zs_pool > *pool)* > to set up max_zpage_size. > Let's hide the allocator's detail to the exported function.
Hi Minchan,
cool :)
I'll re-spin the patch [in a day or two]. and then *may be* we can
return to the huge-class watermark proposition. may be there can be
a knob or something of that kind.
-ss
