public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: "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:59:57 +0100	[thread overview]
Message-ID: <87d4h3pwhe.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081110121123.F82A.E1E9C6FF@jp.fujitsu.com> (Yasunori Goto's message of "Mon, 10 Nov 2008 13:47:51 +0900")

Yasunori Goto <y-goto@jp.fujitsu.com> writes:
>
> However, I think this has the possibility of a finishing blow of OOM.
> For example,
>
>   1) Page caches occupy normal zone, and DMA zone is free.
>   2) A user's application requires a few GB memory and mlock it.
>      All DMA zone is occupied by it.

The VM has special "lower zone protection" to protect against these
kinds of deadlocks. They can be circumvented, but it takes effort.

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

-Andi

-- 
ak@linux.intel.com

  reply	other threads:[~2008-11-10 12:42 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 [this message]
2008-11-10 19:07   ` Robin Holt
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=87d4h3pwhe.fsf@basil.nowhere.org \
    --to=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