mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: <arnd@arndb.de>, <gregkh@linuxfoundation.org>, <sivanich@sgi.com>,
	<ira.weiny@intel.com>, <jglisse@redhat.com>,
	<william.kucharski@oracle.com>, <hch@lst.de>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-kernel-mentees@lists.linuxfoundation.org>
Subject: Re: [Linux-kernel-mentees][PATCH v4 1/1] sgi-gru: Remove *pte_lookup functions
Date: Fri, 9 Aug 2019 11:03:14 -0700	[thread overview]
Message-ID: <f2f928f1-2747-e693-1a7f-14ad5f57fef5@nvidia.com> (raw)
In-Reply-To: <20190809094406.GA22457@bharath12345-Inspiron-5559>

On 8/9/19 2:44 AM, Bharath Vedartham wrote:
> On Thu, Aug 08, 2019 at 04:21:44PM -0700, John Hubbard wrote:
>> On 8/8/19 11:55 AM, Bharath Vedartham wrote:
>> ...
>>>   static int gru_vtop(struct gru_thread_state *gts, unsigned long vaddr,
>>>   		    int write, int atomic, unsigned long *gpa, int *pageshift)
>>>   {
>>>   	struct mm_struct *mm = gts->ts_mm;
>>>   	struct vm_area_struct *vma;
>>>   	unsigned long paddr;
>>> -	int ret, ps;
>>> +	int ret;
>>> +	struct page *page;
>>>   
>>>   	vma = find_vma(mm, vaddr);
>>>   	if (!vma)
>>> @@ -263,21 +187,33 @@ static int gru_vtop(struct gru_thread_state *gts, unsigned long vaddr,
>>>   
>>>   	/*
>>>   	 * Atomic lookup is faster & usually works even if called in non-atomic
>>> -	 * context.
>>> +	 * context. get_user_pages_fast does atomic lookup before falling back to
>>> +	 * slow gup.
>>>   	 */
>>>   	rmb();	/* Must/check ms_range_active before loading PTEs */
>>> -	ret = atomic_pte_lookup(vma, vaddr, write, &paddr, &ps);
>>> -	if (ret) {
>>> -		if (atomic)
>>> +	if (atomic) {
>>> +		ret = __get_user_pages_fast(vaddr, 1, write, &page);
>>> +		if (!ret)
>>>   			goto upm;
>>> -		if (non_atomic_pte_lookup(vma, vaddr, write, &paddr, &ps))
>>> +	} else {
>>> +		ret = get_user_pages_fast(vaddr, 1, write ? FOLL_WRITE : 0, &page);
>>> +		if (!ret)
>>>   			goto inval;
>>>   	}
>>> +
>>> +	paddr = page_to_phys(page);
>>> +	put_user_page(page);
>>> +
>>> +	if (unlikely(is_vm_hugetlb_page(vma)))
>>> +		*pageshift = HPAGE_SHIFT;
>>> +	else
>>> +		*pageshift = PAGE_SHIFT;
>>> +
>>>   	if (is_gru_paddr(paddr))
>>>   		goto inval;
>>> -	paddr = paddr & ~((1UL << ps) - 1);
>>> +	paddr = paddr & ~((1UL << *pageshift) - 1);
>>>   	*gpa = uv_soc_phys_ram_to_gpa(paddr);
>>> -	*pageshift = ps;
>>
>> Why are you no longer setting *pageshift? There are a couple of callers
>> that both use this variable.
> Hi John,
> 
> I did set *pageshift. The if statement above sets *pageshift. ps was
> used to retrive the pageshift value when the pte_lookup functions were
> present. ps was passed by reference to those functions and set by them.
> But here since we are trying to remove those functions, we don't need ps
> and we directly set *pageshift to HPAGE_SHIFT or PAGE_SHIFT based on the
> type of vma.
> 
> Hope this clears things up?
> 

Right you are, sorry for overlooking that. Looks good.

thanks,
-- 
John Hubbard
NVIDIA

  reply	other threads:[~2019-08-09 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 18:55 [Linux-kernel-mentees][PATCH v4 0/1] get_user_pages changes Bharath Vedartham
2019-08-08 18:55 ` [Linux-kernel-mentees][PATCH v4 1/1] sgi-gru: Remove *pte_lookup functions Bharath Vedartham
2019-08-08 23:21   ` John Hubbard
2019-08-08 23:30     ` John Hubbard
2019-08-09  9:44       ` Bharath Vedartham
2019-08-09  9:44     ` Bharath Vedartham
2019-08-09 18:03       ` John Hubbard [this message]
2019-08-09  9:52     ` Bharath Vedartham
  -- strict thread matches above, loose matches on Subject: below --
2019-07-30 15:39 [Linux-kernel-mentees][PATCH v4 0/1] get_user_pages changes Bharath Vedartham
2019-07-30 15:39 ` [Linux-kernel-mentees][PATCH v4 1/1] sgi-gru: Remove *pte_lookup functions Bharath Vedartham

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=f2f928f1-2747-e693-1a7f-14ad5f57fef5@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=ira.weiny@intel.com \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux.bhar@gmail.com \
    --cc=sivanich@sgi.com \
    --cc=william.kucharski@oracle.com \
    /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

Powered by JetHome