[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d4h3pwhe.fsf@basil.nowhere.org>
Date: Mon, 10 Nov 2008 13:59:57 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Yasunori Goto <y-goto@...fujitsu.com>
Cc: "Luck, Tony" <tony.luck@...el.com>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
linux-ia64@...r.kernel.org,
Linux Kernel ML <linux-kernel@...r.kernel.org>,
Joerg Roedel <joerg.roedel@....com>
Subject: Re: [Q] Why does dma_alloc_coherent() of ia64 GFP_DMA?
Yasunori Goto <y-goto@...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@...ux.intel.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists