Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932329AbWBCE6Y (ORCPT ); Thu, 2 Feb 2006 23:58:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751154AbWBCE6Y (ORCPT ); Thu, 2 Feb 2006 23:58:24 -0500 Received: from main.gmane.org ([80.91.229.2]:18640 "EHLO ciao.gmane.org") by vger.kernel.org with ESMTP id S1750944AbWBCE6X (ORCPT ); Thu, 2 Feb 2006 23:58:23 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: yipee Subject: Re: changing physical page Date: Fri, 3 Feb 2006 04:58:07 +0000 (UTC) Message-ID: References: A Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 87.69.73.167 (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 21 linux-os (Dick Johnson analogic.com> writes: [snip] > If your program(s) rely upon being in some physical location, > they are broken. Even with mlockall(), you just keep them > where they are, not where you'd like them to be. If you > are trying to DMA into/out-of user-space, there is only > ONE way to do it. Your driver allocates DMA-able pages and > your code mmaps() it into user-space. That way, the page(s) > are always present and have the right attributes. If you > malloc() something, then try to "convert" in the kernel > through your driver, the code's broken. And all this page-moving for getting contiguous DMA memory, happens today on x86_64 kernels? Can you please give me a pointer to the source code? 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/