Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750709AbWCOUKb (ORCPT ); Wed, 15 Mar 2006 15:10:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750744AbWCOUKb (ORCPT ); Wed, 15 Mar 2006 15:10:31 -0500 Received: from nommos.sslcatacombnetworking.com ([67.18.224.114]:57490 "EHLO nommos.sslcatacombnetworking.com") by vger.kernel.org with ESMTP id S1750709AbWCOUKa (ORCPT ); Wed, 15 Mar 2006 15:10:30 -0500 In-Reply-To: References: <20060315193114.GA7465@in.ibm.com> <1142452665.3021.43.camel@laptopd505.fenrus.org> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Arjan van de Ven , vgoyal@in.ibm.com, linux kernel mailing list , Fastboot mailing list , "Eric W. Biederman" , Morton Andrew Morton , gregkh@suse.de Content-Transfer-Encoding: 7bit From: Kumar Gala Subject: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource" Date: Wed, 15 Mar 2006 14:10:59 -0600 To: Kumar Gala X-Mailer: Apple Mail (2.746.3) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - nommos.sslcatacombnetworking.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - kernel.crashing.org X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1388 Lines: 38 On Mar 15, 2006, at 2:01 PM, Kumar Gala wrote: > > On Mar 15, 2006, at 1:57 PM, Arjan van de Ven wrote: > >> >>> One of the possible solutions to this problem is that expand the >>> size >>> of "start" and "end" to "unsigned long long". But whole of the >>> PCI and >>> driver code has been written assuming start and end to be >>> unsigned long >>> and compiler starts throwing warnings. >> >> >> please use dma_addr_t then instead of unsigned long long >> >> this is the right size on all platforms afaik (could a ppc64 person >> verify this?> ;) > > Actually we really just want "start" and "end" to be u64 on all > platforms. Linus was ok with this change but no one has gone > through and fixed everything that would be required for it. As my memory comes back to me on this. I also believe that Andrew asked me for size comparisons between a kernel using 32-bit start/end and 64-bit start/end on a 32-bit machine for a allyesconfig build. I don't believe I ever got around to doing this or reporting the numbers to him. It would be useful to have both code size differences and run time (if possible). - kumar - 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/