From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
Kyeongdon Kim <kyeongdon.kim@lge.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH v4 0/2] zram/zcomp: stream allocation fixes and tweaks
Date: Tue, 1 Dec 2015 21:36:28 +0900 [thread overview]
Message-ID: <1448973390-21170-1-git-send-email-sergey.senozhatsky@gmail.com> (raw)
Hello,
Two patches that address possible issues with compression
stream allocations under low memory or heavy fragmentation conditions.
These patches are considered to be a -stable material, however there
is no Cc -stable on "zram: try vmalloc() after kmalloc()" as of now.
We'd like to ask Kyeongdon to re-test and re-confirm (the patch has
been modified).
V4:
-- do not use __GFP_NOMEMALLOC for zcomp private allocation. thanks
to Kyeongdon Kim for doing a good job testing and to Minchan Kim for
analysis.
V3,V2,V1: tweaking GFP flags, etc.
Kyeongdon Kim (1):
zram: try vmalloc() after kmalloc()
Sergey Senozhatsky (1):
zram/zcomp: use GFP_NOIO to allocate streams
drivers/block/zram/zcomp.c | 4 ++--
drivers/block/zram/zcomp_lz4.c | 23 +++++++++++++++++++++--
drivers/block/zram/zcomp_lzo.c | 23 +++++++++++++++++++++--
3 files changed, 44 insertions(+), 6 deletions(-)
--
2.6.2
next reply other threads:[~2015-12-01 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 12:36 Sergey Senozhatsky [this message]
2015-12-01 12:36 ` [PATCH v4 1/2] zram/zcomp: use GFP_NOIO to allocate streams Sergey Senozhatsky
2015-12-01 12:36 ` [PATCH v4 2/2] zram: try vmalloc() after kmalloc() Sergey Senozhatsky
2015-12-18 0:28 ` Sergey Senozhatsky
2015-12-22 3:10 ` Kyeongdon Kim
2015-12-22 6:54 ` Sergey Senozhatsky
2015-12-22 6:59 ` Sergey Senozhatsky
2015-12-22 15:23 ` Greg KH
2015-12-23 9:25 ` Sergey Senozhatsky
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=1448973390-21170-1-git-send-email-sergey.senozhatsky@gmail.com \
--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 \
/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).