From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751835AbZHZQTm (ORCPT ); Wed, 26 Aug 2009 12:19:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751771AbZHZQTl (ORCPT ); Wed, 26 Aug 2009 12:19:41 -0400 Received: from mail-bw0-f219.google.com ([209.85.218.219]:33086 "EHLO mail-bw0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751734AbZHZQTk (ORCPT ); Wed, 26 Aug 2009 12:19:40 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=vx00hNmece/fUexARNutX4FJxlTiINbwLbdTP4HCt6K57unWPM78tnyNT4fAsGZEqr UZ+kZTuE34CvjqOpNhOrSvfD/CAQgSXpXUYdmZh8PWW+eKLjMl1s3n8t7w71Y9wkTkQU 3V7P04qfMWLmMxBYGkJSyeirQZFGQJBsh++Gs= MIME-Version: 1.0 In-Reply-To: References: <200908241007.47910.ngupta@vflare.org> <84144f020908241033l4af09e7h9caac47d8d9b7841@mail.gmail.com> <4A92EBB4.1070101@vflare.org> <4A930313.9070404@vflare.org> <4A93FAA5.5000001@vflare.org> <4A94358C.6060708@vflare.org> Date: Wed, 26 Aug 2009 19:19:40 +0300 X-Google-Sender-Auth: 3a2eb100610ac6a8 Message-ID: <84144f020908260919ke9d6c34qb47c3015ee0ca89b@mail.gmail.com> Subject: Re: [PATCH 1/4] compcache: xvmalloc memory allocator From: Pekka Enberg To: Christoph Lameter Cc: Nitin Gupta , Hugh Dickins , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mm-cc@laptop.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Aug 2009, Nitin Gupta wrote: >> I went crazy. I meant 40 bits for PFN -- not 48. This 40-bit PFN should be >> sufficient for all archs. For archs where 40 + PAGE_SHIFT < MAX_PHYSMEM_BITS >> ramzswap will just issue a compiler error. On Wed, Aug 26, 2009 at 7:10 PM, Christoph Lameter wrote: > How about restricting the xvmalloc memory allocator to 32 bit? If I > understand correctly xvmalloc main use in on 32 bit in order to be > able to use HIGHMEM? That was the main reason for a specialized allocator rather than trying to use SLOB. However, if "xvmalloc" is merged with ramzswap, it makes sense to use it on desktop class 64-bit machines as well. Pekka 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 082D96B006A for ; Wed, 26 Aug 2009 12:19:35 -0400 (EDT) Received: by bwz24 with SMTP id 24so261799bwz.38 for ; Wed, 26 Aug 2009 09:19:41 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <200908241007.47910.ngupta@vflare.org> <84144f020908241033l4af09e7h9caac47d8d9b7841@mail.gmail.com> <4A92EBB4.1070101@vflare.org> <4A930313.9070404@vflare.org> <4A93FAA5.5000001@vflare.org> <4A94358C.6060708@vflare.org> Date: Wed, 26 Aug 2009 19:19:40 +0300 Message-ID: <84144f020908260919ke9d6c34qb47c3015ee0ca89b@mail.gmail.com> Subject: Re: [PATCH 1/4] compcache: xvmalloc memory allocator From: Pekka Enberg Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Christoph Lameter Cc: Nitin Gupta , Hugh Dickins , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mm-cc@laptop.org List-ID: On Wed, 26 Aug 2009, Nitin Gupta wrote: >> I went crazy. I meant 40 bits for PFN -- not 48. This 40-bit PFN should be >> sufficient for all archs. For archs where 40 + PAGE_SHIFT < MAX_PHYSMEM_BITS >> ramzswap will just issue a compiler error. On Wed, Aug 26, 2009 at 7:10 PM, Christoph Lameter wrote: > How about restricting the xvmalloc memory allocator to 32 bit? If I > understand correctly xvmalloc main use in on 32 bit in order to be > able to use HIGHMEM? That was the main reason for a specialized allocator rather than trying to use SLOB. However, if "xvmalloc" is merged with ramzswap, it makes sense to use it on desktop class 64-bit machines as well. Pekka -- 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