Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1316670 > unrolled thread
| Started by | Sergey Senozhatsky <sergey.senozhatsky@gmail.com> |
|---|---|
| First post | 2016-01-25 14:00 +0100 |
| Last post | 2016-01-25 14:10 +0100 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.kernel
[stable] upstream d913897abace8 -stable backport request Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-01-25 14:00 +0100
Re: [stable] upstream d913897abace8 -stable backport request Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-01-25 14:10 +0100
| From | Sergey Senozhatsky <sergey.senozhatsky@gmail.com> |
|---|---|
| Date | 2016-01-25 14:00 +0100 |
| Subject | [stable] upstream d913897abace8 -stable backport request |
| Message-ID | <qUOUq-40h-25@gated-at.bofh.it> |
Hello,
Please add upstream 'commit d913897abace8 ("zram: try vmalloc() after
kmalloc()")' to stable releases.
:commit d913897abace843bba20249f3190167f7895e9c3
:Author: Kyeongdon Kim <kyeongdon.kim@lge.com>
:
: 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
[toc] | [next] | [standalone]
| From | Sergey Senozhatsky <sergey.senozhatsky@gmail.com> |
|---|---|
| Date | 2016-01-25 14:10 +0100 |
| Message-ID | <qUP46-4jX-11@gated-at.bofh.it> |
| In reply to | #1316670 |
On (01/25/16 21:50), Sergey Senozhatsky wrote:
> Hello,
>
> Please add upstream 'commit d913897abace8 ("zram: try vmalloc() after
> kmalloc()")' to stable releases.
>
[v3.15+]
-ss
> :commit d913897abace843bba20249f3190167f7895e9c3
> :Author: Kyeongdon Kim <kyeongdon.kim@lge.com>
> :
> : 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
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web