From: Matthew Wilcox <matthew@wil.cx>
To: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Hans J. Koch" <hjk@hansjkoch.de>, Greg KH <gregkh@suse.de>,
tglx@linutronix.de, linux-pci@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: extra large DMA buffer for PCI-E device under UIO
Date: Tue, 22 Nov 2011 10:27:25 -0700 [thread overview]
Message-ID: <20111122172725.GK4387@parisc-linux.org> (raw)
In-Reply-To: <40906F5E-5E97-44CF-AB95-40355204B63F@gmail.com>
On Tue, Nov 22, 2011 at 11:54:22AM -0500, Jean-Francois Dagenais wrote:
> That is quite interesting. It really seems like my VT-d recipe to create 128MB for my PCI-e
> FPGA to write into is covered by this patch.
>
> My problem is that our FPGA is connected to one of the atom E6XX's PCI-e links, so no
> iommu :( Since our first product had VT-d, the FPGA, uio based module and userspace
> code is designed such that the device sees a huge contiguous memory chunk. This is key
> to the performance of the FPGA, which is essentially decoupled from the CPU for it's real-time
> acquisition.
Is it really key? If you supported, ohidon'tknow, 2MB pages, you'd
need 64 entries in the FPGA to store the addresses of those 2MB pages,
which doesn't sound like a huge burden.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2011-11-22 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 21:16 extra large DMA buffer for PCI-E device under UIO Jean-Francois Dagenais
2011-11-18 22:08 ` Greg KH
2011-11-21 15:31 ` Jean-Francois Dagenais
2011-11-21 17:36 ` Greg KH
2011-11-21 18:17 ` Hans J. Koch
[not found] ` <4A52B447-8E21-43F6-A38E-711E36F89A34@gmail.com>
2011-11-21 19:29 ` Hans J. Koch
2011-11-22 15:24 ` Jean-Francois Dagenais
2011-11-22 15:35 ` Michael S. Tsirkin
2011-11-22 16:54 ` Jean-Francois Dagenais
2011-11-22 17:27 ` Matthew Wilcox [this message]
2011-11-22 17:40 ` Michael S. Tsirkin
2011-11-22 17:37 ` Michael S. Tsirkin
2011-11-22 17:54 ` Hans J. Koch
2011-11-22 18:40 ` Michael S. Tsirkin
2011-11-22 18:52 ` Hans J. Koch
2011-11-22 19:50 ` Jean-Francois Dagenais
2011-11-23 8:20 ` Michael S. Tsirkin
2011-11-22 16:05 ` Hans J. Koch
2011-11-22 19:57 ` Jean-Francois Dagenais
2013-01-23 2:00 ` Jean-François Dagenais
2011-11-18 22:27 ` Hans J. Koch
2011-11-21 15:10 ` Jean-Francois Dagenais
2011-11-21 15:47 ` Rolf Eike Beer
2011-11-21 16:01 ` Jean-Francois Dagenais
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=20111122172725.GK4387@parisc-linux.org \
--to=matthew@wil.cx \
--cc=gregkh@suse.de \
--cc=hjk@hansjkoch.de \
--cc=jeff.dagenais@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=tglx@linutronix.de \
/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