From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f51.google.com ([209.85.220.51]:36818 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755781AbcAYNCo (ORCPT ); Mon, 25 Jan 2016 08:02:44 -0500 Date: Mon, 25 Jan 2016 22:00:54 +0900 From: Sergey Senozhatsky To: Sergey Senozhatsky Cc: stable@vger.kernel.org, Minchan Kim , Andrew Morton , Kyeongdon Kim , linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [stable] upstream d913897abace8 -stable backport request Message-ID: <20160125130054.GC526@swordfish> References: <20160125125051.GB526@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160125125051.GB526@swordfish> Sender: stable-owner@vger.kernel.org List-ID: 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 > : > : 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 >