linux-kernel - Re: [PATCH 1/2] Generic Virtual Memmap suport for SPARSEMEM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1175551505.22373.126.camel@localhost.localdomain>
Date:	Mon, 02 Apr 2007 15:05:05 -0700
From:	Dave Hansen <hansendc@...ibm.com>
To:	Christoph Lameter <clameter@....com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Martin Bligh <mbligh@...gle.com>, linux-mm@...ck.org,
	Andi Kleen <ak@...e.de>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH 1/2] Generic Virtual Memmap suport for SPARSEMEM

On Mon, 2007-04-02 at 14:53 -0700, Christoph Lameter wrote:
> > > Well think about how to handle the case that the allocatiopn of a page 
> > > table page or a vmemmap block fails. Once we have that sorted out then we 
> > > can cleanup the higher layers.
> > 
> > I think it is best to just completely replace
> > sparse_early_mem_map_alloc() for the vmemmap case.  It really is a
> > completely different beast.  You'd never, for instance, have
> > alloc_remap() come into play.
> 
> What is the purpose of alloc_remap? Could not figure that one out.

That's what we use on i386 to get some lowmem area for non-zero NUMA
nodes.  Otherwise, all of ZONE_NORMAL is on node 0.  It's a bit hokey,
and stuff like virt_to_phys() probably doesn't work on it, but it has
worked pretty well for a long time.  

-- Dave

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