Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1189993 > unrolled thread

Re: [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT

Started byPaul Gortmaker <paul.gortmaker@windriver.com>
First post2015-07-22 16:20 +0200
Last post2015-07-22 16:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT Paul Gortmaker <paul.gortmaker@windriver.com> - 2015-07-22 16:20 +0200

#1189993 — Re: [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT

FromPaul Gortmaker <paul.gortmaker@windriver.com>
Date2015-07-22 16:20 +0200
SubjectRe: [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT
Message-ID<pP32i-Ny-9@gated-at.bofh.it>
On 2015-07-21 11:37 AM, Eric B Munson wrote:
> On Mon, 20 Jul 2015, Chris Metcalf wrote:
> 
>> On 07/18/2015 03:11 PM, Paul Gortmaker wrote:
>>> On Tue, Jul 7, 2015 at 1:03 PM, Eric B Munson<emunson@akamai.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@akamai.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.
> 
> Thanks for the offer, I think I have is sorted in V4 (which I am
> checking one last time before I post).

Not quite sorted yet.  Seems parisc fails on v4.  It updated the
number of syscalls but did not update syscall_table.S causing:

arch/parisc/kernel/syscall_table.S:444: Error: size of syscall table does not fit value of __NR_Linux_syscalls

http://kisskb.ellerman.id.au/kisskb/buildresult/12468884/

Paul.
--

> Eric
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web