Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932358AbVLHWYw (ORCPT ); Thu, 8 Dec 2005 17:24:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932392AbVLHWYw (ORCPT ); Thu, 8 Dec 2005 17:24:52 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72]:2601 "EHLO sj-iport-3.cisco.com") by vger.kernel.org with ESMTP id S932358AbVLHWYv (ORCPT ); Thu, 8 Dec 2005 17:24:51 -0500 X-IronPort-AV: i="3.99,232,1131350400"; d="scan'208"; a="375861452:sNHT1872012770" To: Kumar Gala Cc: Jeff Garzik , Andrew Grover , , , , Subject: Re: [RFC] [PATCH 0/3] ioat: DMA engine support X-Message-Flag: Warning: May contain useful information References: From: Roland Dreier Date: Thu, 08 Dec 2005 14:23:40 -0800 In-Reply-To: (Kumar Gala's message of "Thu, 8 Dec 2005 16:13:52 -0600 (CST)") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 08 Dec 2005 22:23:41.0220 (UTC) FILETIME=[0AFD2640:01C5FC46] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 711 Lines: 16 Kumar> I'm actually searching for any examples of drivers that Kumar> deal with the issues related to DMA'ng directly two and Kumar> from user space memory. It's not quite the same story as what you're doing with DMA engines inside the CPU, but you could look at drivers/infiniband, particularly drivers/infiniband/core/uverbs_mem.c. That handles pinning and getting DMA addresses for user memory that will be used as a DMA target in the future. - R. - 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/