From: "Uroš Golob" <uros.golob@i-tech.si>
To: linux-mm@kvack.org
Cc: "Uroš Golob" <uros.golob@i-tech.si>
Subject: how to acquire large DMA buffes in 64bit kernel
Date: Mon, 4 Mar 2013 11:33:08 +0100 [thread overview]
Message-ID: <F12E8BD2FBBBAA4C98474AAA7FA1599101574ECE@it-dc.i-tech.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Hello fellow developers,
I am researching possibilities to acquire large DMA contiguous memory for our new device. Plan is to develop Linux driver for our new product with MicroTCA Kontron board with Intel i7 and 4GB ram (there is slim possibility to get 8GB system). In the same system (crate) user could plug in up to 10 custom devices (that is our new product with fpga chip and pcie interface), each board requires 4 32MB buffers in kernel module. So on end of day I would like to have from 128 to 1280MB of memory, depends of number of devices plugged into system. I know that it is possible to use scatter gather for DMA, but there is shortage of descriptors in our fpga chip...
I have come to some problems/questions and I can't find answer to, I did use google and read ton of documentation, books, forums, etc... with no luck...
- Does Contiguous Memory Allocator support x86_64 platform? And if, how to configure kernel ( because there is conflict between SWIOTLB and HAVE_DMA_CONTIGOUS).
- Is there any working bigphysarea patch for Linux kernel 3.2.x (or newer) for x86_64 platform (I know that there is for x86_32, but wit 32 bit kernel I could get only 512MB of contiguous memory).
I must confess I am total noob in device driver development, so what am I missing? Is there any other way to acquire large buffers in Linux kernel module? Am I just way too greedy with contiguous memory?
Best regards,
Uros
[-- Attachment #2: Type: text/html, Size: 1885 bytes --]
reply other threads:[~2013-03-04 10:33 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=F12E8BD2FBBBAA4C98474AAA7FA1599101574ECE@it-dc.i-tech.local \
--to=uros.golob@i-tech.si \
--cc=linux-mm@kvack.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