From: Andrew Morton <akpm@linux-foundation.org>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: Linux-mm@kvack.org, Ira Weiny <ira.weiny@intel.com>,
Mike Rapoport <rppt@linux.ibm.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
John Hubbard <jhubbard@nvidia.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5] mm/gup: speed up check_and_migrate_cma_pages() on huge page
Date: Thu, 27 Jun 2019 16:25:11 -0700 [thread overview]
Message-ID: <20190627162511.1cf10f5b04538c955c329408@linux-foundation.org> (raw)
In-Reply-To: <1561612545-28997-1-git-send-email-kernelfans@gmail.com>
On Thu, 27 Jun 2019 13:15:45 +0800 Pingfan Liu <kernelfans@gmail.com> wrote:
> Both hugetlb and thp locate on the same migration type of pageblock, since
> they are allocated from a free_list[]. Based on this fact, it is enough to
> check on a single subpage to decide the migration type of the whole huge
> page. By this way, it saves (2M/4K - 1) times loop for pmd_huge on x86,
> similar on other archs.
>
> Furthermore, when executing isolate_huge_page(), it avoid taking global
> hugetlb_lock many times, and meanless remove/add to the local link list
> cma_page_list.
>
Thanks, looks good to me. Have any timing measurements been taken?
> ...
>
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -1336,25 +1336,30 @@ static long check_and_migrate_cma_pages(struct task_struct *tsk,
> struct vm_area_struct **vmas,
> unsigned int gup_flags)
> {
> - long i;
> + long i, step;
I'll make these variables unsigned long - to match nr_pages and because
we have no need for them to be negative.
> ...
next prev parent reply other threads:[~2019-06-27 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 5:15 Pingfan Liu
2019-06-27 23:25 ` Andrew Morton [this message]
2019-06-28 3:59 ` Pingfan Liu
2019-06-27 23:38 ` Ira Weiny
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=20190627162511.1cf10f5b04538c955c329408@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=Linux-mm@kvack.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jhubbard@nvidia.com \
--cc=keith.busch@intel.com \
--cc=kernelfans@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=mike.kravetz@oracle.com \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
/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