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
| ||
|
Date: Tue, 27 May 2014 11:31:21 -0500 (CDT) From: Christoph Lameter <cl@...two.org> To: Peter Zijlstra <peterz@...radead.org> cc: Konstantin Khlebnikov <koct9i@...il.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, Hugh Dickins <hughd@...gle.com>, Mel Gorman <mgorman@...e.de>, Roland Dreier <roland@...nel.org>, Sean Hefty <sean.hefty@...el.com>, Hal Rosenstock <hal.rosenstock@...il.com>, Mike Marciniszyn <infinipath@...el.com> Subject: Re: [RFC][PATCH 0/5] VM_PINNED On Tue, 27 May 2014, Peter Zijlstra wrote: > On Tue, May 27, 2014 at 10:14:10AM -0500, Christoph Lameter wrote: > > On Tue, 27 May 2014, Peter Zijlstra wrote: > > > > > Well, like with IB, they start out as normal userspace pages, and will > > > be from ZONE_MOVABLE. > > > > Well we could change that now I think. If the VMA has VM_PINNED set > > pages then do not allocate from ZONE_MOVABLE. > > But most allocations sites don't have the vma. We allocate page-cache > pages based on its address_space/mapping, not on whatever vma they're > mapped into. Most allocations by the application for an address range also must consider a memory allocation policy which is also bound to a vma and we have code for that in mm/mempolicy.c Code could be easily added to alloc_pages_vma() to consider the pinned status on allocation. Remove GFP_MOVABLE if the vma is pinned. -- 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/
Powered by blists - more mailing lists