On (02/22/16 10:34), Minchan Kim wrote: [..] > > > I tempted it several times with same reason you pointed out. > > > But my worry was that if we increase ZS_MAX_ZSPAGE_ORDER, zram can > > > consume more memory because we need several pages chain to populate > > > just a object. Even, at that time, we didn't have compaction scheme > > > so fragmentation of object in zspage is huge pain to waste memory. > > > > well, the thing is -- we end up requesting less pages after all, so > > zsmalloc has better chances to survive. for example, gcc5 compilation test > > Indeed. I saw your test result. [..] > > Total 129 489 1627756 1618193 850147 > > > > > > that's 891703 - 850147 = 41556 less pages. or 162MB less memory used. > > 41556 less pages means that zsmalloc had 41556 less chances to fail. > > > Let's think swap-case which is more important for zram now. As you know, > most of usecase are swap in embedded world. > Do we really need 16 pages allocator for just less PAGE_SIZE objet > at the moment which is really heavy memory pressure? I'll take a look at dynamic class page addition. -ss -- 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>