[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55AD5CB9.4090400@ezchip.com>
Date: Mon, 20 Jul 2015 16:40:25 -0400
From: Chris Metcalf <cmetcalf@...hip.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>,
Eric B Munson <emunson@...mai.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.cz>,
Vlastimil Babka <vbabka@...e.cz>,
LKML <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
linux-arch <linux-arch@...r.kernel.org>,
<linux-api@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Re: [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT
On 07/18/2015 03:11 PM, Paul Gortmaker wrote:
> On Tue, Jul 7, 2015 at 1:03 PM, Eric B Munson<emunson@...mai.com> wrote:
>> >The cost of faulting in all memory to be locked can be very high when
>> >working with large mappings. If only portions of the mapping will be
>> >used this can incur a high penalty for locking.
>> >
>> >Now that we have the new VMA flag for the locked but not present state,
>> >expose it as an mmap option like MAP_LOCKED -> VM_LOCKED.
> An automatic bisection on arch/tile leads to this commit:
>
> 5a5656f2c9b61c74c15f9ef3fa2e6513b6c237bb is the first bad commit
> commit 5a5656f2c9b61c74c15f9ef3fa2e6513b6c237bb
> Author: Eric B Munson<emunson@...mai.com>
> Date: Thu Jul 16 10:09:22 2015 +1000
>
> mm: mmap: add mmap flag to request VM_LOCKONFAULT
Eric, I'm happy to help with figuring out the tile issues.
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
--
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