> -----Original Message----- > From: Davidlohr Bueso [mailto:d...@stgolabs.net] > Sent: Wednesday, February 06, 2019 5:32 PM > To: j...@ziepe.ca; a...@linux-foundation.org > Cc: dledf...@redhat.com; j...@mellanox.com; j...@suse.cz; > wi...@infradead.org; Weiny, Ira <ira.we...@intel.com>; linux- > r...@vger.kernel.org; linux...@kvack.org; linux-kernel@vger.kernel.org > 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 <dbu...@suse.de>
Reviewed-by: Ira Weiny <ira.we...@intel.com> > --- > 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
