From: "\"Ing. Daniel Rozsnyó\"" <daniel@rozsnyo.com>
To: linux-kernel@vger.kernel.org
Subject: Provision for direct device to device DMA
Date: Sun, 27 Apr 2014 09:47:33 +0200 [thread overview]
Message-ID: <535CB615.7070504@rozsnyo.com> (raw)
We are working on a product with PCIe based backplane (with PLX switch
chips) to connect various high-bandwidth devices (namely an image sensor
and multiple SSDs). The Linux system runs on a small (ARM based)
processor, which has limited memory bandwidth (32bit/800MHz) and more
importantly limited PCIe bandwidth (x1 root port). From linux sources,
we could understand, that all DMA is towards or from system memory,
which is the bottleneck in our use case (we peak at 2000MB/s).
What is the advised way of doing disk i/o with data coming from/to
another PCIe device? We would prefer to keep a filesystem on the target
drives, but it is not a hard requirement. The storage solution is AHCI
(multiple ASM1061) and the other end are our FPGA devices. For future,
it would be nice to stream over PCIe fabric into a 10GE nic, like i82599
(ixgbe), from both the storage and from FPGA.
Do we need to write a kernel module to handle such transfers on a very
low level (like a combined ahci-fpga-nic driver)?
Or a special mmap() before write() would auto-magically do the right job?
Thank you,
Daniel Rozsnyo
reply other threads:[~2014-04-27 7:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=535CB615.7070504@rozsnyo.com \
--to=daniel@rozsnyo.com \
--cc=linux-kernel@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