Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753999AbbK0ELP (ORCPT ); Thu, 26 Nov 2015 23:11:15 -0500 Received: from mail-pa0-f46.google.com ([209.85.220.46]:33752 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753983AbbK0ELM (ORCPT ); Thu, 26 Nov 2015 23:11:12 -0500 From: Sergey Senozhatsky X-Google-Original-From: Sergey Senozhatsky To: Andrew Morton Cc: Minchan Kim , Kyeongdon Kim , linux-kernel@vger.kernel.org, Sergey Senozhatsky , Sergey Senozhatsky Subject: [PATCH v3 0/2] zram/zcomp: stream allocation fixes and tweaks Date: Fri, 27 Nov 2015 13:10:47 +0900 Message-Id: <1448597449-17579-1-git-send-email-sergey.senozhatsky@gmail.com> X-Mailer: git-send-email 2.6.3.368.gf34be46 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1224 Lines: 33 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). I split the patch set into separate threads. Two more patches - zram: pass gfp from zcomp frontend to backend (Minchan Kim) - zram/zcomp: do not zero out zcomp private pages (Sergey Senozhatsky) (not a -stable material) will be posted separately. 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.3.368.gf34be46 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/