From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755714AbbINNtG (ORCPT ); Mon, 14 Sep 2015 09:49:06 -0400 Received: from mail-la0-f50.google.com ([209.85.215.50]:33574 "EHLO mail-la0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755681AbbINNtE (ORCPT ); Mon, 14 Sep 2015 09:49:04 -0400 Date: Mon, 14 Sep 2015 15:49:01 +0200 From: Vitaly Wool To: minchan@kernel.org, sergey.senozhatsky@gmail.com, ddstreet@ieee.org Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH 0/3] allow zram to use zbud as underlying allocator Message-Id: <20150914154901.92c5b7b24e15f04d8204de18@gmail.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While using ZRAM on a small RAM footprint devices, together with KSM, I ran into several occasions when moving pages from compressed swap back into the "normal" part of RAM caused significant latencies in system operation. By using zbud I lose in compression ratio but gain in determinism, lower latencies and lower fragmentation, so in the coming patches I tried to generalize what I've done to enable zbud for zram so far. -- Vitaly Wool