linux-kernel - Re: [PATCH 1/11] Add __GFP_MOVABLE flag and update callers

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: <1164153096.9131.74.camel@localhost.localdomain>
Date:	Tue, 21 Nov 2006 15:51:36 -0800
From:	Dave Hansen <haveblue@...ibm.com>
To:	Mel Gorman <mel@....ul.ie>
Cc:	Christoph Lameter <clameter@....com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/11] Add __GFP_MOVABLE flag and update callers

On Tue, 2006-11-21 at 23:43 +0000, Mel Gorman wrote:
> On Tue, 21 Nov 2006, Christoph Lameter wrote:
> > Are GFP_HIGHUSER allocations always movable? It would reduce the size of
> > the patch if this would be added to GFP_HIGHUSER.
> 
> No, they aren't. Page tables allocated with HIGHPTE are currently not 
> movable for example. A number of drivers (infiniband for example) also use 
> __GFP_HIGHMEM that are not movable.

I think Christoph was saying that it might reduce the size of the patch
to include it by _default_.  You could always go to the
weird^Wspecialized users and mask the bits back off.

We probably also need to start getting a nice list of those users which
are HIGH but not MOVABLE.  This would provide that by default, I think.

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