Re: [PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation

On (03/11/16 16:30), Minchan Kim wrote: [..] > init > Node 0, zone DMA208120 51 41 11 0 0 0 > 0 0 0 > Node 0, zoneDMA32 16380 13777 9184 3805789 54 3 0 > 0 0 0 > compaction > Node 0, zone DMA

Re: [PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation

On (03/11/16 16:30), Minchan Kim wrote: [..] > init > Node 0, zone DMA208120 51 41 11 0 0 0 > 0 0 0 > Node 0, zoneDMA32 16380 13777 9184 3805789 54 3 0 > 0 0 0 > compaction > Node 0, zone DMA

[PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation

Zsmalloc is ready for page migration so zram can use __GFP_MOVABLE from now on. I did test to see how it helps to make higher order pages. Test scenario is as follows. KVM guest, 1G memory, ext4 formated zram block device, for i in `seq 1 8`; do dd if=/dev/vda1 of=mnt/test$i.txt bs=128M

[PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation

Zsmalloc is ready for page migration so zram can use __GFP_MOVABLE from now on. I did test to see how it helps to make higher order pages. Test scenario is as follows. KVM guest, 1G memory, ext4 formated zram block device, for i in `seq 1 8`; do dd if=/dev/vda1 of=mnt/test$i.txt bs=128M