From: Robin Holt <holt@sgi.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
"Luck, Tony" <tony.luck@intel.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-ia64@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [Q] Why does dma_alloc_coherent() of ia64 GFP_DMA?
Date: Mon, 10 Nov 2008 13:07:11 -0600 [thread overview]
Message-ID: <20081110190711.GG8483@sgi.com> (raw)
In-Reply-To: <87d4h3pwhe.fsf@basil.nowhere.org>
On Mon, Nov 10, 2008 at 01:59:57PM +0100, Andi Kleen wrote:
> Yasunori Goto <y-goto@jp.fujitsu.com> writes:
> > 3) A device which allows over 4GB is hot-added.
> > But dma_alloc_coherent() try to allocate DMA zone.
> > Then OOM occurs because there is no freeable pages.
> >
> > I heard there are some users who require a few GB mlock.
>
> Normally mlock is limited to half the memory exactly to avoid
> such problems.
>
> Also I believe there are some issues with non continuous memory on
> some IA64 systems -- e.g. Altixes iirc have the requirement
> that you use the IOMMU for higher memory. So it's probably
> not easy to change.
I am not sure what is be referred to here, but all of an Altix's memory is
DMA capable with the exception of the stuff covered by the MSPEC driver
(that is uncached memory). There are certainly all sort of special
requirements for doing transfers on Altix to eliminate memory ordering
problems, but nothing specific that I recall related to address ranges
and DMA.
I appologize in advance if I am answering a different question that
was asked.
Thanks,
Robin
next prev parent reply other threads:[~2008-11-10 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 4:47 [Q] Why does dma_alloc_coherent() of ia64 GFP_DMA? Yasunori Goto
2008-11-10 12:59 ` Andi Kleen
2008-11-10 19:07 ` Robin Holt [this message]
2008-11-10 21:57 ` Christoph Lameter
2008-11-11 5:14 ` Yasunori Goto
2008-11-11 5:48 ` FUJITA Tomonori
2008-11-10 22:06 ` Christoph Lameter
2008-11-11 5:39 ` Yasunori Goto
2008-11-11 20:34 ` Christoph Lameter
2008-11-11 5:53 ` FUJITA Tomonori
2008-11-11 20:32 ` Christoph Lameter
2008-11-12 1:40 ` FUJITA Tomonori
2008-11-11 5:41 ` FUJITA Tomonori
2008-11-11 6:21 ` Yasunori Goto
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=20081110190711.GG8483@sgi.com \
--to=holt@sgi.com \
--cc=andi@firstfloor.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=joerg.roedel@amd.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=y-goto@jp.fujitsu.com \
/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