From: Steve Capper <steve.capper@arm.com>
To: Chanho Park <chanho61.park@samsung.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Inki Dae <inki.dae@samsung.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Myungjoo Ham <myungjoo.ham@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Grazvydas Ignotas <notasas@gmail.com>
Subject: Re: [PATCH] arm: mm: lockless get_user_pages_fast
Date: Fri, 5 Apr 2013 12:11:59 +0100 [thread overview]
Message-ID: <20130405111158.GA13428@e103986-lin> (raw)
In-Reply-To: <1360890012-4684-1-git-send-email-chanho61.park@samsung.com>
Hi Chanho,
Apologies for the tardy response, this patch slipped past me.
On Fri, Feb 15, 2013 at 01:00:12AM +0000, Chanho Park wrote:
> This patch adds get_user_pages_fast(old name is "fast_gup") for ARM.
> The fast_gup can walk pagetable without taking mmap_sem or any locks. If there
> is not a pte with the correct permissions for the access, we fall back to slow
> path(get_user_pages) to get remaining pages. This patch is written on reference
> the x86's gup implementation. Traversing of hugepages is excluded because ARM
> haven't supported hugepages yet[1], just only RFC.
>
I've tested this patch out, unfortunately it treats huge pmds as regular
pmds and attempts to traverse them rather than fall back to a slow path.
The fix for this is very minor, please see my suggestion below.
As an aside, I would like to extend this fast_gup to include full huge
page support and include a __get_user_pages_fast implementation. This
will hopefully fix a problem that was brought to my attention by
Grazvydas Ignotas whereby a FUTEX_WAIT on a THP tail page will cause
an infinite loop due to the stock implementation of __get_user_pages_fast
always returning 0.
> diff --git a/arch/arm/mm/gup.c b/arch/arm/mm/gup.c
> new file mode 100644
> index 0000000..ed54fd8
...
> +static int gup_pmd_range(pud_t *pudp, unsigned long addr, unsigned long end,
> + int write, struct page **pages, int *nr)
> +{
> + unsigned long next;
> + pmd_t *pmdp;
> +
> + pmdp = pmd_offset(pudp, addr);
> + do {
> + next = pmd_addr_end(addr, end);
> + if (pmd_none(*pmdp))
> + return 0;
I would suggest:
if (pmd_none(*pmdp) || pmd_bad(*pmdp))
return 0;
as this will pick up pmds that can't be traversed, and fall back to the slow path.
> + else if (!gup_pte_range(pmdp, addr, next, write, pages, nr))
> + return 0;
> + } while (pmdp++, addr = next, addr != end);
> +
> + return 1;
> +}
> +
Cheers,
--
Steve
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-05 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 1:00 [PATCH] arm: mm: lockless get_user_pages_fast Chanho Park
2013-04-05 11:11 ` Steve Capper [this message]
2013-04-10 7:30 ` Chanho Park
2013-04-10 8:21 ` Steve Capper
2013-04-10 9:10 ` Chanho Park
2013-04-10 9:47 ` Steve Capper
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=20130405111158.GA13428@e103986-lin \
--to=steve.capper@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=chanho61.park@samsung.com \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=myungjoo.ham@samsung.com \
--cc=notasas@gmail.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;
as well as URLs for NNTP newsgroup(s).