From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with SMTP id EF79E6B004D for ; Fri, 14 Aug 2009 00:54:04 -0400 (EDT) Received: by rv-out-0708.google.com with SMTP id l33so301631rvb.26 for ; Thu, 13 Aug 2009 21:54:11 -0700 (PDT) Message-ID: <4A84EDE4.1080605@vflare.org> Date: Fri, 14 Aug 2009 10:23:56 +0530 From: Nitin Gupta Reply-To: ngupta@vflare.org MIME-Version: 1.0 Subject: Re: compcache as a pre-swap area References: <200908122007.43522.ngupta@vflare.org> <200908130805.36787.a1426z@gawab.com> <200908140702.23947.a1426z@gawab.com> In-Reply-To: <200908140702.23947.a1426z@gawab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Al Boldi Cc: Hugh Dickins , Matthew Wilcox , Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On 08/14/2009 09:32 AM, Al Boldi wrote: > Nitin Gupta wrote: >> compcache is really not really a swap replacement. Its just another >> swap device that >> compresses data and stores it in memory itself. You can have disk >> based swaps along >> with ramzswap (name of block device). > > So once compcache fills up, it will start to age its contents into normal > swap? > This is desirable but not yet implemented. For now, if 'backing swap' is used, compcache will forward incompressible pages to the backing swap device. If compcache fills up, kernel will simply send further swap-outs to swap device which comes next in priority. Nitin -- 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