linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jason Gunthorpe <jgg@ziepe.ca>, <linux-rdma@vger.kernel.org>,
	<linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] IB/umem: use get_user_pages_fast() to pin DMA pages
Date: Mon, 11 Nov 2019 13:44:07 -0800	[thread overview]
Message-ID: <1730ced5-a280-1825-54fe-61b9340f8ac6@nvidia.com> (raw)
In-Reply-To: <20191111032111.GA30123@iweiny-DESK2.sc.intel.com>

On 11/10/19 7:21 PM, Ira Weiny wrote:
> On Fri, Nov 08, 2019 at 06:04:34PM -0800, John Hubbard wrote:
>> And get rid of the mmap_sem calls, as part of that. Note
>> that get_user_pages_fast() will, if necessary, fall back to
>> __gup_longterm_unlocked(), which takes the mmap_sem as needed.
>>
>> Cc: Jason Gunthorpe <jgg@ziepe.ca>
>> Cc: Ira Weiny <ira.weiny@intel.com>
> 
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> 

Thanks for the review, Ira! This will show up shortly, in the v3
series of "mm/gup: track dma-pinned pages: FOLL_PIN, FOLL_LONGTERM".


thanks,
-- 
John Hubbard
NVIDIA

>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>> ---
>>  drivers/infiniband/core/umem.c | 17 ++++++-----------
>>  1 file changed, 6 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/infiniband/core/umem.c b/drivers/infiniband/core/umem.c
>> index 24244a2f68cc..3d664a2539eb 100644
>> --- a/drivers/infiniband/core/umem.c
>> +++ b/drivers/infiniband/core/umem.c
>> @@ -271,16 +271,13 @@ struct ib_umem *ib_umem_get(struct ib_udata *udata, unsigned long addr,
>>  	sg = umem->sg_head.sgl;
>>  
>>  	while (npages) {
>> -		down_read(&mm->mmap_sem);
>> -		ret = get_user_pages(cur_base,
>> -				     min_t(unsigned long, npages,
>> -					   PAGE_SIZE / sizeof (struct page *)),
>> -				     gup_flags | FOLL_LONGTERM,
>> -				     page_list, NULL);
>> -		if (ret < 0) {
>> -			up_read(&mm->mmap_sem);
>> +		ret = get_user_pages_fast(cur_base,
>> +					  min_t(unsigned long, npages,
>> +						PAGE_SIZE /
>> +						sizeof(struct page *)),
>> +					  gup_flags | FOLL_LONGTERM, page_list);
>> +		if (ret < 0)
>>  			goto umem_release;
>> -		}
>>  
>>  		cur_base += ret * PAGE_SIZE;
>>  		npages   -= ret;
>> @@ -288,8 +285,6 @@ struct ib_umem *ib_umem_get(struct ib_udata *udata, unsigned long addr,
>>  		sg = ib_umem_add_sg_table(sg, page_list, ret,
>>  			dma_get_max_seg_size(context->device->dma_device),
>>  			&umem->sg_nents);
>> -
>> -		up_read(&mm->mmap_sem);
>>  	}
>>  
>>  	sg_mark_end(sg);
>> -- 
>> 2.24.0
>>
> 


  reply	other threads:[~2019-11-11 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09  2:04 [PATCH 0/1] IB/umem: use get_user_pages_fast() to pin DMA pages John Hubbard
2019-11-09  2:04 ` [PATCH 1/1] " John Hubbard
2019-11-11  3:21   ` Ira Weiny
2019-11-11 21:44     ` John Hubbard [this message]
2019-11-12 20:29   ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1730ced5-a280-1825-54fe-61b9340f8ac6@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=ira.weiny@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).