Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759239AbZCYKmV (ORCPT ); Wed, 25 Mar 2009 06:42:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754368AbZCYKmJ (ORCPT ); Wed, 25 Mar 2009 06:42:09 -0400 Received: from ti-out-0910.google.com ([209.85.142.187]:18948 "EHLO ti-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753611AbZCYKmH (ORCPT ); Wed, 25 Mar 2009 06:42:07 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=CITaGONEidSSSFrIn8NXlMud7kMjtrmJwDOb4M+RKX6gcHj7YHLOeWyK2VXPaubsJp hQU276M1lT8QaeET1oFDWplaxVICkWjkDFbzoZNNn7jhqaNKR0VnE/vpMr1hmDcTJEF8 stWz3HW2mBceYzK7simDUwwR/GsRXdpqXXt2A= Message-ID: <49CA09F4.5050104@vflare.org> Date: Wed, 25 Mar 2009 16:09:48 +0530 From: Nitin Gupta Reply-To: ngupta@vflare.org User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Christoph Lameter , Andrew Morton , Pekka Enberg CC: "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 0/3] compressed in-memory swapping take3 References: <49C92E14.5060802@vflare.org> In-Reply-To: <49C92E14.5060802@vflare.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2132 Lines: 63 Hi, Maybe it simply got lost in LKML traffic. Any chance it can make it into 2.6.30?? Thanks, Nitin Nitin Gupta wrote: > > Project home: http://code.google.com/p/compcache/ > > It allows creating a RAM based block device which acts as swap disk. > Pages swapped to this device are compressed and stored in memory itself. > This is a big win over swapping to slow hard-disk which are typically used > as swap disk. For flash, these suffer from wear-leveling issues when used > as swap disk - so again its helpful. For swapless systems, it allows more > apps to run. > > > * Changelog: take3 vs take2 > xvmalloc changes: > - Use kernel defined macros and constants in xvmalloc and remove > equivalent defines for ALIGN, roundup etc. > - Use kernel bitops (set_bit, clear_bit) > - Moved it to drivers/block since its not clear if it has any other > user. > ramzswap changes: > - All instances of compcache renamed to ramzswap. > Also renamed module to ramzswap > - Renamed "backing_dev" parameter to "backing_swap" > - Documentation changes to reflect above changes. > - Remove "table index" from object header (4 bytes). This will be > needed when memory defragmentation is implemented. So, avoid this > (small) overhead for now. > > > * Changelog: take2 vs initial revision: > xvmalloc changes: > - Use Linux kernel coding style for xvmalloc > - Collapse all individual flag test/set/get to generic {test_set_get}_flag > - Added BLOCK_NEXT() macro to reach next contiguous block > - Other minor cleanups - no functional changes > compcache block device code: > - compcache core changes due to change in xvmalloc interface names > > > Links to performance numbers, use cases can be found in original thread: > http://lkml.org/lkml/2009/3/17/116 > > Thanks to Christoph, Pekka and Andrew for feedback on previous revisions. > > Thanks, > Nitin > -- 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/