linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Nazarewicz" <mina86@mina86.com>
To: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: use of alloc_bootmem for a PCI-e device
Date: Wed, 23 Nov 2011 22:31:40 +0100	[thread overview]
Message-ID: <op.v5e4q2ug3l0zgt@mpn-glaptop> (raw)
In-Reply-To: <DEF7AFA8-9119-4FD7-915E-FB8572F06F02@gmail.com>

> On Nov 23, 2011, at 14:31, Michal Nazarewicz wrote:
>> 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.

On Wed, 23 Nov 2011 22:21:15 +0100, Jean-Francois Dagenais <jeff.dagenais@gmail.com> wrote:
> Looks like it can do what I want. Are there any mainline merge plans?

There are plans...  Execution is uncertain. ;)

> Unless I am mistaken, because of SWIOTLB, only x86_32 is supported, correct?
>
> Since I want to allocate the buffer once at startup, then keep it until shutdown,
> can you suggest a simpler, less flexible alternative?

Oh no, I wouldn't recommend using the full CMA for your purpose, but no matter
there is a piece of code that does what you need.  Marek has added support for
Intel so it should work for you as well, even though I have had a chance to
run that piece yet.

You are interested in parts of patch 8[1] (namely dma_declare_contiguous()
function) and the last hunk of patch 9[2] (namely the part where
dma_contiguous_reserve() is called).

[1] http://article.gmane.org/gmane.linux.kernel.mm/70321
[2] http://article.gmane.org/gmane.linux.kernel.mm/70318

-- 
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>

      reply	other threads:[~2011-11-23 21:31 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
2011-11-23 21:21   ` Jean-Francois Dagenais
2011-11-23 21:31     ` Michal Nazarewicz [this message]

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.v5e4q2ug3l0zgt@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