From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: stable@vger.kernel.org, Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kyeongdon Kim <kyeongdon.kim@lge.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [stable] upstream d913897abace8 -stable backport request
Date: Mon, 25 Jan 2016 22:00:54 +0900 [thread overview]
Message-ID: <20160125130054.GC526@swordfish> (raw)
In-Reply-To: <20160125125051.GB526@swordfish>
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
>
prev parent reply other threads:[~2016-01-25 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 12:50 [stable] upstream d913897abace8 -stable backport request Sergey Senozhatsky
2016-01-25 13:00 ` Sergey Senozhatsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160125130054.GC526@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kyeongdon.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).