Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755741Ab0KHWne (ORCPT ); Mon, 8 Nov 2010 17:43:34 -0500 Received: from smtp-out.google.com ([216.239.44.51]:30064 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753310Ab0KHWnd convert rfc822-to-8bit (ORCPT ); Mon, 8 Nov 2010 17:43:33 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=C8t4qxjBNpPh2XM1n5zMJ1zKp+frvNoadDDIH7HBDc49y8JgLDlvvC8r0J0vY4GMsv Csk37fgtdAfHzC07WieA== MIME-Version: 1.0 In-Reply-To: <20101108223838.GM23393@cmpxchg.org> References: <1288973333-7891-1-git-send-email-minchan.kim@gmail.com> <20101106010357.GD23393@cmpxchg.org> <20101107215030.007259800@cmpxchg.org> <20101107220353.115646194@cmpxchg.org> <20101108223838.GM23393@cmpxchg.org> From: Greg Thelen Date: Mon, 8 Nov 2010 14:43:11 -0800 Message-ID: Subject: Re: [patch 1/4] memcg: use native word to represent dirtyable pages To: Johannes Weiner Cc: Minchan Kim , Andrew Morton , Dave Young , Andrea Righi , KAMEZAWA Hiroyuki , Daisuke Nishimura , Balbir Singh , Wu Fengguang , linux-mm@kvack.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1192 Lines: 25 On Mon, Nov 8, 2010 at 2:38 PM, Johannes Weiner wrote: > On Mon, Nov 08, 2010 at 02:25:15PM -0800, Greg Thelen wrote: >> Minchan Kim writes: >> >> > On Mon, Nov 8, 2010 at 7:14 AM, Johannes Weiner wrote: >> >> The memory cgroup dirty info calculation currently uses a signed >> >> 64-bit type to represent the amount of dirtyable memory in pages. >> >> >> >> This can instead be changed to an unsigned word, which will allow the >> >> formula to function correctly with up to 160G of LRU pages on a 32-bit >> Is is really 160G of LRU pages? ?On 32-bit machine we use a 32 bit >> unsigned page number. ?With a 4KiB page size, I think that maps 16TiB >> (1<<(32+12)) bytes. ?Or is there some other limit? > > Yes, the dirty limit we calculate from it :) > > We have to be able to multiply this number by up to 100 (maximum dirty > ratio value) without overflowing. Duh :) thanks. -- 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/