linux-kernel - Re: [RFC][PATCH 3/9] mm: page->pfmemalloc only used by slab/skb

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: <52D5B762.3090209@sr71.net>
Date:	Tue, 14 Jan 2014 14:17:06 -0800
From:	Dave Hansen <dave@...1.net>
To:	Christoph Lameter <cl@...ux.com>
CC:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, penberg@...nel.org
Subject: Re: [RFC][PATCH 3/9] mm: page->pfmemalloc only used by slab/skb

On 01/14/2014 11:49 AM, Christoph Lameter wrote:
> On Tue, 14 Jan 2014, Dave Hansen wrote:
>> page->pfmemalloc does not deserve a spot in 'struct page'.  It is
>> only used transiently _just_ after a page leaves the buddy
>> allocator.
> 
> Why would we need to do this if we are removing the cmpxchg_double?

Why do we need the patch?

'struct page' is a mess.  It's really hard to follow, and the space in
the definition is a limited resource.  We should not waste that space on
such a transient and unimportant value as pfmemalloc.
--
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/