From: "Michal Nazarewicz" <mina86@mina86.com>
To: linux-mm@kvack.org, Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Subject: Re: use of alloc_bootmem for a PCI-e device
Date: Wed, 23 Nov 2011 20:31:55 +0100 [thread overview]
Message-ID: <op.v5ey7hv93l0zgt@mpn-glaptop> (raw)
In-Reply-To: <9AF7658D-FEDB-479A-8D4F-A54264363CB4@gmail.com>
On Wed, 23 Nov 2011 20:30:30 +0100, Jean-Francois Dagenais <jeff.dagenais@gmail.com> wrote:
> I am maintaining a kernel for an embedded product. We have an FPGA
> acquisition device interfaced through PCI-e on different intel platforms.
> The acquisition device needs an extra large physically contiguous memory
> area to autonomously dump acquired data into.
[...]
> We are doing another incarnation of the product on an Atom E6xx which has
> no such IOMMU and am looking into ways of allocating a huge chunk of ram.
> Kind of like integrated gfx chips do with RAM, but I don't have the assistance
> of the BIOS.
One trick that you might try to use (even though it's a bit hackish) is to
pass ram=### on Linux command line where the number passed is actual memory
minus size of the buffer you need. Other then that, you might take a look
at CMA (CMAv17 it was sent last week or so to linux-mm) which in one of the
initialisation steps needs to grab memory regions.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-23 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 19:30 Jean-Francois Dagenais
2011-11-23 19:31 ` Michal Nazarewicz [this message]
2011-11-23 21:21 ` Jean-Francois Dagenais
2011-11-23 21:31 ` Michal Nazarewicz
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=op.v5ey7hv93l0zgt@mpn-glaptop \
--to=mina86@mina86.com \
--cc=jeff.dagenais@gmail.com \
--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