Re: [PATCH 1/5] vrange: Add vrange syscall and handle splitting/merging and marking vmas

Hey Kosaki-san, Sorry to not have replied to this earlier, I really appreciate your review! I'm now running through your feedback to make sure its all integrated into my upcoming v13 patch series, and while most of your comments have been addressed there are a few items outstanding, which I susp

Re: [PATCH 1/5] vrange: Add vrange syscall and handle splitting/merging and marking vmas

On Sun, Mar 23, 2014 at 5:20 AM, Jan Kara wrote: > On Fri 21-03-14 14:17:31, John Stultz wrote: >> RETURN VALUE >> On success vrange returns the number of bytes marked or unmarked. >> Similar to write(), it may return fewer bytes then specified >> if it ran into a problem. >> >>

Re: [PATCH 1/5] vrange: Add vrange syscall and handle splitting/merging and marking vmas

Hi On Fri, Mar 21, 2014 at 2:17 PM, John Stultz wrote: > This patch introduces the vrange() syscall, which allows for specifying > ranges of memory as volatile, and able to be discarded by the system. > > This initial patch simply adds the syscall, and the vma handling, > splitting and merging th

Re: [PATCH 1/5] vrange: Add vrange syscall and handle splitting/merging and marking vmas

On Fri 21-03-14 14:17:31, John Stultz wrote: > This patch introduces the vrange() syscall, which allows for specifying > ranges of memory as volatile, and able to be discarded by the system. > > This initial patch simply adds the syscall, and the vma handling, > splitting and merging the vmas as n

[PATCH 1/5] vrange: Add vrange syscall and handle splitting/merging and marking vmas

This patch introduces the vrange() syscall, which allows for specifying ranges of memory as volatile, and able to be discarded by the system. This initial patch simply adds the syscall, and the vma handling, splitting and merging the vmas as needed, and marking them with VM_VOLATILE. No purging o