Skip to contentSkip to conversation

upstream d913897abace8 -stable backport request

stable Sergey Senozhatsky 1 participant 2 messages Jan 25, 2016 Stable branch

lore
Share & tools
lore
#0 lore raw

Hello,

Please add upstream 'commit d913897abace8 ("zram: try vmalloc() after kmalloc()")' to stable releases.

:commit d913897abace843bba20249f3190167f7895e9c3
:Author: Kyeongdon Kim <[email protected]>
:
: zram: try vmalloc() after kmalloc()
:

:    When we're using LZ4 multi compression streams for zram swap, we found
:    out page allocation failure message in system running test.  That was
:    not only once, but a few(2 - 5 times per test).  Also, some failure
:    cases were continually occurring to try allocation order 3.
:    
:    In order to make parallel compression private data, we should call
:    kzalloc() with order 2/3 in runtime(lzo/lz4).  But if there is no order
:    2/3 size memory to allocate in that time, page allocation fails.  This
:    patch makes to use vmalloc() as fallback of kmalloc(), this prevents
:    page alloc failure warning.

:
: After using this, we never found warning message in running test, also
: It could reduce process startup latency about 60-120ms in each case.

	-ss
#1 lore raw
Quoted 5 lines · Sergey Senozhatsky

Hello,

Please add upstream 'commit d913897abace8 ("zram: try vmalloc() after kmalloc()")' to stable releases.

[v3.15+]

	-ss
Quoted 21 lines

:commit d913897abace843bba20249f3190167f7895e9c3
:Author: Kyeongdon Kim <[email protected]>
:
: zram: try vmalloc() after kmalloc()
:

:    When we're using LZ4 multi compression streams for zram swap, we found
:    out page allocation failure message in system running test.  That was
:    not only once, but a few(2 - 5 times per test).  Also, some failure
:    cases were continually occurring to try allocation order 3.
:    
:    In order to make parallel compression private data, we should call
:    kzalloc() with order 2/3 in runtime(lzo/lz4).  But if there is no order
:    2/3 size memory to allocate in that time, page allocation fails.  This
:    patch makes to use vmalloc() as fallback of kmalloc(), this prevents
:    page alloc failure warning.

:
: After using this, we never found warning message in running test, also
: It could reduce process startup latency about 60-120ms in each case.

	-ss