From: Roland Dreier <rdreier@cisco.com>
To: Kumar Gala <galak@gate.crashing.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Andrew Grover <andrew.grover@intel.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <john.ronciak@intel.com>,
<christopher.leech@intel.com>
Subject: Re: [RFC] [PATCH 0/3] ioat: DMA engine support
Date: Thu, 08 Dec 2005 14:23:40 -0800 [thread overview]
Message-ID: <ada4q5jz0r7.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0512081606060.24134-100000@gate.crashing.org> (Kumar Gala's message of "Thu, 8 Dec 2005 16:13:52 -0600 (CST)")
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.
next prev parent reply other threads:[~2005-12-08 22:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 20:26 [RFC] [PATCH 0/3] ioat: DMA engine support Andrew Grover
2005-11-23 22:06 ` Jeff Garzik
2005-11-23 22:30 ` Andi Kleen
2005-11-23 23:02 ` Jeff Garzik
2005-11-24 0:05 ` Alan Cox
2005-11-23 23:36 ` Jeff Garzik
2005-11-24 0:17 ` Benjamin LaHaise
2005-11-24 0:50 ` David S. Miller
2005-11-24 6:50 ` Andi Kleen
2005-11-24 15:24 ` Avi Kivity
2005-11-24 15:29 ` Andi Kleen
2005-11-24 15:35 ` Avi Kivity
2005-11-24 15:37 ` Andi Kleen
2005-11-23 22:54 ` Alan Cox
2005-11-23 22:56 ` Jeff Garzik
2005-12-08 22:13 ` Kumar Gala
2005-12-08 22:23 ` Roland Dreier [this message]
2005-12-08 22:42 ` Alan Cox
2005-12-09 7:12 ` Evgeniy Polyakov
2005-11-23 22:45 ` Jeff Garzik
2005-12-02 17:06 ` Jon Mason
2005-11-23 22:53 ` Jeff Garzik
2005-11-23 23:02 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ada4q5jz0r7.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=andrew.grover@intel.com \
--cc=christopher.leech@intel.com \
--cc=galak@gate.crashing.org \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).