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: <Pine.LNX.4.64.0611241009100.6991@woody.osdl.org>
Date:	Fri, 24 Nov 2006 10:11:55 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Christoph Lameter <clameter@....com>
cc:	Mel Gorman <mel@...net.ie>, linux-mm@...ck.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/11] Add __GFP_MOVABLE flag and update callers

On Fri, 24 Nov 2006, Christoph Lameter wrote:
> 
> So please do not require movable pages to be user allocations.

I don't think you read the whole sentence I wrote.

Go back: USER just means "it it can fail much more eagerly". It really has 
nothing to do with user-mode per se. It's just not so core that the kernel 
cannot handle allocation failures, so it doesn't get to retry the 
allocation so eagerly.

THAT is why "movable" is almost guaranteed to also imply USER. Not because 
it's not a "kernel" allocation. After all, _all_ page allocations are 
kernel allocations, it's just that some are more likely to be associated 
with direct user requests, and some are more internal.

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