From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756154AbbLAMiI (ORCPT ); Tue, 1 Dec 2015 07:38:08 -0500 Received: from mail-pa0-f47.google.com ([209.85.220.47]:33215 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754254AbbLAMiF (ORCPT ); Tue, 1 Dec 2015 07:38:05 -0500 From: Sergey Senozhatsky To: Andrew Morton Cc: Minchan Kim , Kyeongdon Kim , linux-kernel@vger.kernel.org, Sergey Senozhatsky , Sergey Senozhatsky Subject: [PATCH v4 0/2] zram/zcomp: stream allocation fixes and tweaks Date: Tue, 1 Dec 2015 21:36:28 +0900 Message-Id: <1448973390-21170-1-git-send-email-sergey.senozhatsky@gmail.com> X-Mailer: git-send-email 2.6.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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