From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764326AbYEAVCS (ORCPT ); Thu, 1 May 2008 17:02:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756815AbYEAVCH (ORCPT ); Thu, 1 May 2008 17:02:07 -0400 Received: from yw-out-2324.google.com ([74.125.46.28]:57313 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754458AbYEAVCE (ORCPT ); Thu, 1 May 2008 17:02:04 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MlKCgrUN98onAo/oi2NUJZavYqil8MRi9uy3w9ZalgsHFmgCc4E3Yt3DdJmxrSZby8A7ajxrEiJSS5sTKRYEALSGjvEcS5dSlOQVa8Xr0Xw0lpcqmEzlkMaEfMNH57npuM8qor91vUZQlbbj8ah2+18z3WmsvLSWAqL8F6PFbcQ= Message-ID: <86802c440805011402h1e452b57ma27ffa6ad7b50238@mail.gmail.com> Date: Thu, 1 May 2008 14:02:01 -0700 From: "Yinghai Lu" To: "H. Peter Anvin" Subject: Re: [PATCH] x86: mtrr cleanup for converting continuous to discrete - auto detect v2 Cc: "Andrew Morton" , "Ingo Molnar" , "Thomas Gleixner" , "Gabriel C" , "Mika Fischer" , "linux-kernel@vger.kernel.org" In-Reply-To: <481A1D3A.5040202@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200804272337.40130.yhlu.kernel@gmail.com> <200804292025.58268.yhlu.kernel@gmail.com> <200805010100.34751.yhlu.kernel@gmail.com> <200805011157.00693.yhlu.kernel@gmail.com> <481A1D3A.5040202@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 1, 2008 at 12:42 PM, H. Peter Anvin wrote: > Yinghai Lu wrote: > > > loop mtrr chunk_size and gran_size from 1M to 2G to find out optimal > value. > > > > Why stopping at 2 GB? if you select 4g for chunk size, we don't need to convert that from continuous to discrete to make X server driver happen. actually the code could support any chunk_size... for example: 16 g system orginal: 0-4g WB 3.5g-4g UC 4g-8g WB 8g-16g WB 16g-16.5g WB if you set chunk size to 16g, and gran size <= 512M you will get 0-16g WB 3.5g-4g UC 16g-16.5g WB YH