[PATCH v2 2/3] mm/gup: introduce FOLL_PIN flag for get_user_pages()

As explained in the newly added documentation for FOLL_PIN and FOLL_LONGTERM, in every case where vaddr_pin_pages() is required, FOLL_PIN must be set. That reason, plus a desire to keep FOLL_PIN an internal (to get_user_pages() and follow_page()) detail, is why vaddr_pin_pages() sets FOLL_PIN.

Re: [RFC PATCH v2 2/3] mm/gup: introduce FOLL_PIN flag for get_user_pages()

On 8/16/19 7:36 PM, John Hubbard wrote: On 8/16/19 7:24 PM, jhubb...@nvidia.com wrote: From: John Hubbard DKIM-Signature: v
a a-sha256; claxed/relaxed; d idia.com; s
; t66008674; bhMai0va6k/z2enpQJ4Nfvbj5WByFxGAO1JwdIBbXioh

Re: [RFC PATCH v2 2/3] mm/gup: introduce FOLL_PIN flag for get_user_pages()

On 8/16/19 7:24 PM, jhubb...@nvidia.com wrote: > From: John Hubbard > DKIM-Signature: v
a a-sha256; claxed/relaxed; d idia.com; s
; > t66008674; bhMai0va6k/z2enpQJ4Nfvbj5WByFxGAO1JwdIBbXioh > PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer: >

[RFC PATCH v2 2/3] mm/gup: introduce FOLL_PIN flag for get_user_pages()

From: John Hubbard DKIM-Signature: v
a* - * In the CMA case: longterm pins in a CMA region would unnecessarily fragment - * that region. And so CMA attempts to migrate the page before pinning when + * In the CMA case: long term pins in a CMA region would unnecessarily fragment + * that region.