Re: [PATCH v2 0/3] mm/gup: introduce vaddr_pin_pages_remote(), FOLL_PIN

On 8/22/19 5:24 PM, Ira Weiny wrote: > On Tue, Aug 20, 2019 at 09:07:24PM -0700, John Hubbard wrote: >> Hi Ira, >> >> This is for your tree. I'm dropping the RFC because this aspect is >> starting to firm up pretty well. >> >> I've moved FOLL_PIN inside the vaddr_pin_*() routines, and moved >>

Re: [PATCH v2 0/3] mm/gup: introduce vaddr_pin_pages_remote(), FOLL_PIN

On Tue, Aug 20, 2019 at 09:07:24PM -0700, John Hubbard wrote: > Hi Ira, > > This is for your tree. I'm dropping the RFC because this aspect is > starting to firm up pretty well. > > I've moved FOLL_PIN inside the vaddr_pin_*() routines, and moved > FOLL_LONGTERM outside, based on our recent

[PATCH v2 0/3] mm/gup: introduce vaddr_pin_pages_remote(), FOLL_PIN

Hi Ira, This is for your tree. I'm dropping the RFC because this aspect is starting to firm up pretty well. I've moved FOLL_PIN inside the vaddr_pin_*() routines, and moved FOLL_LONGTERM outside, based on our recent discussions. This is documented pretty well within the patches. Note that there

[RFC PATCH v2 0/3] mm/gup: introduce vaddr_pin_pages_remote(), FOLL_PIN

From: John Hubbard Hi Ira, As requested, this is for your tree: https://github.com/weiny2/linux-kernel.git (mmotm-rdmafsdax-b0-v4), to be applied at your last authored commit, which is: commit f625f92ecfb4 ("mm/gup: Remove FOLL_LONGTERM DAX exclusion"). In other words, please delete my previous