RE: [PATCH 7/6] Documentation/infiniband: update from locked to pinned_vm

[Weiny, Ira]

> -----Original Message-----
> From: Davidlohr Bueso [mailto:dave@xxxxxxxxxxxx]
> Sent: Wednesday, February 06, 2019 5:32 PM
> To: jgg@xxxxxxxx; akpm@xxxxxxxxxxxxxxxxxxxx
> Cc: dledford@xxxxxxxxxx; jgg@xxxxxxxxxxxx; jack@xxxxxxx;
> willy@xxxxxxxxxxxxx; Weiny, Ira <ira.weiny@xxxxxxxxx>; linux-
> rdma@xxxxxxxxxxxxxxx; linux-mm@xxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
> Subject: [PATCH 7/6] Documentation/infiniband: update from locked to
> pinned_vm
> 
> We are really talking about pinned_vm here.
> 
> Signed-off-by: Davidlohr Bueso <dbueso@xxxxxxx>

Reviewed-by: Ira Weiny <ira.weiny@xxxxxxxxx>

> ---
>  Documentation/infiniband/user_verbs.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/infiniband/user_verbs.txt
> b/Documentation/infiniband/user_verbs.txt
> index df049b9f5b6e..47ebf2f80b2b 100644
> --- a/Documentation/infiniband/user_verbs.txt
> +++ b/Documentation/infiniband/user_verbs.txt
> @@ -46,11 +46,11 @@ Memory pinning
>    I/O targets be kept resident at the same physical address.  The
>    ib_uverbs module manages pinning and unpinning memory regions via
>    get_user_pages() and put_page() calls.  It also accounts for the
> -  amount of memory pinned in the process's locked_vm, and checks that
> +  amount of memory pinned in the process's pinned_vm, and checks that
>    unprivileged processes do not exceed their RLIMIT_MEMLOCK limit.
> 
>    Pages that are pinned multiple times are counted each time they are
> -  pinned, so the value of locked_vm may be an overestimate of the
> +  pinned, so the value of pinned_vm may be an overestimate of the
>    number of pages pinned by a process.
> 
>  /dev files
> --
> 2.16.4