From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757201AbcAYMwm (ORCPT ); Mon, 25 Jan 2016 07:52:42 -0500 Received: from mail-pf0-f181.google.com ([209.85.192.181]:33639 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755781AbcAYMwk (ORCPT ); Mon, 25 Jan 2016 07:52:40 -0500 Date: Mon, 25 Jan 2016 21:50:51 +0900 From: Sergey Senozhatsky To: stable@vger.kernel.org Cc: Minchan Kim , Andrew Morton , Kyeongdon Kim , linux-kernel@vger.kernel.org, Sergey Senozhatsky , Sergey Senozhatsky Subject: [stable] upstream d913897abace8 -stable backport request Message-ID: <20160125125051.GB526@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Please add upstream 'commit d913897abace8 ("zram: try vmalloc() after kmalloc()")' to stable releases. :commit d913897abace843bba20249f3190167f7895e9c3 :Author: Kyeongdon Kim : : 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