From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qe0-f47.google.com (mail-qe0-f47.google.com [209.85.128.47]) by kanga.kvack.org (Postfix) with ESMTP id C58476B0031 for ; Fri, 3 Jan 2014 10:12:01 -0500 (EST) Received: by mail-qe0-f47.google.com with SMTP id t7so15391486qeb.6 for ; Fri, 03 Jan 2014 07:12:01 -0800 (PST) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [2607:f8b0:4003:c01::22d]) by mx.google.com with ESMTPS id el7si59379994qeb.29.2014.01.03.07.12.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Jan 2014 07:12:00 -0800 (PST) Received: by mail-ob0-f173.google.com with SMTP id gq1so15613595obb.4 for ; Fri, 03 Jan 2014 07:12:00 -0800 (PST) Date: Fri, 3 Jan 2014 09:11:54 -0600 From: Seth Jennings Subject: Re: [PATCH] mm/zswap: add writethrough option Message-ID: <20140103151154.GA2940@cerebellum.variantweb.net> References: <1387459407-29342-1-git-send-email-ddstreet@ieee.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1387459407-29342-1-git-send-email-ddstreet@ieee.org> Sender: owner-linux-mm@kvack.org List-ID: To: Dan Streetman Cc: Linux-MM , linux-kernel , Bob Liu , Minchan Kim , Weijie Yang , Shirish Pargaonkar , Mel Gorman , Andrew Morton On Thu, Dec 19, 2013 at 08:23:27AM -0500, Dan Streetman wrote: > Currently, zswap is writeback cache; stored pages are not sent > to swap disk, and when zswap wants to evict old pages it must > first write them back to swap cache/disk manually. This avoids > swap out disk I/O up front, but only moves that disk I/O to > the writeback case (for pages that are evicted), and adds the > overhead of having to uncompress the evicted pages and the > need for an additional free page (to store the uncompressed page). > > This optionally changes zswap to writethrough cache by enabling > frontswap_writethrough() before registering, so that any > successful page store will also be written to swap disk. The > default remains writeback. To enable writethrough, the param > zswap.writethrough=1 must be used at boot. > > Whether writeback or writethrough will provide better performance > depends on many factors including disk I/O speed/throughput, > CPU speed(s), system load, etc. In most cases it is likely > that writeback has better performance than writethrough before > zswap is full, but after zswap fills up writethrough has > better performance than writeback. > > Signed-off-by: Dan Streetman Hey Dan, sorry for the delay on this. Vacation and busyness. This looks like a good option for those that don't mind having the write overhead to ensure that things don't really bog down if the compress pool overflows, while maintaining the read fault speedup by decompressing from the pool. Acked-by: Seth Jennings -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org