[lkml]   [2008]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] mm: fix boundary checking in free_bootmem_core
On Fri, Mar 14, 2008 at 09:44:50AM -0700, Yinghai Lu wrote:
> On 14 Mar 2008 12:58:44 +0100, Andi Kleen <> wrote:
> > "Yinghai Lu" <> writes:
> > >
> > > then i tried to reserve 64M or 128M RAM before that, and free that
> > > before gart/switotble try to allloc_bootmem under 4g.
> >
> > Sounds like an incredible hack. There are far better ways to do that
> > for bootmem allocations. e.g. you can just specify a high enough "goal"
> > That is how swiotlb solves a similar problem (at least before my
> > mask allocator rewrite)
> I don't think so.
> anyway, otherway to workaround it is
> change
> return __earlyonly_bootmem_alloc(node, size, size,
> in vmemmap_alloc_block to
> return __earlyonly_bootmem_alloc(node, size, size,
> __pa(MAX_DMA_ADDRESS + (1<<27)));
> to make room for gart. but that is global change. and may affect other
> platform.

You can just make it an optional architecture defined macro

> and don't make sure gart will get it.

Has nothing to do with the gart?

> also i assume swiotlb need that range is less than 4g.

The normal rule is that anybody who needs big bootmem allocations
need to make sure they're high enough to not fill up first 4GB.
For small allocations like most of bootmem it doesn't matter because
they're, um, small.

If vmemmap doesn't do that vmemmap needs to be fixed.


 \ /
  Last update: 2008-03-14 17:53    [W:0.045 / U:2.472 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site