Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Jul 2001 17:54:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Jul 2001 17:54:36 -0400 Received: from weta.f00f.org ([203.167.249.89]:64642 "HELO weta.f00f.org") by vger.kernel.org with SMTP id ; Wed, 11 Jul 2001 17:54:25 -0400 Date: Thu, 12 Jul 2001 09:54:21 +1200 From: Chris Wedgwood To: Jes Sorensen Cc: "David S. Miller" , Alan Cox , Jeff Garzik , Ben LaHaise , "\"MEHTA,HIREN (A-SanJose,ex1)\"" , "'linux-kernel@vger.kernel.org'" Subject: Re: (reposting) how to get DMA'able memory within 4GB on 64-bit m Message-ID: <20010712095421.A2298@weta.f00f.org> In-Reply-To: <3B46FDF1.A38E5BB6@mandrakesoft.com> <15175.2003.773317.101601@pizda.ninka.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 11, 2001 at 09:16:50PM +0200, Jes Sorensen wrote: The overhead is going be negligeble, the overhead of highmem itself is much worse. Not to mention that today some dma_addr_t's might not be packed properly in data structure hence they ending up taking 8 bytes anyway. What kind of packing makes a 32-bit value take 8-bytes on any currently supported archicture? The worst-case I can think of is 7-bytes in the case of misaligned by 3 (e.g. __attribute__((packed)) struct blah { char foo[3]; long bar }; sort of thing). --cw - 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/