linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chanho Park <chanho61.park@samsusng.com>
To: 'Steve Capper' <steve.capper@arm.com>
Cc: 'Chanho Park' <chanho61.park@samsung.com>,
	linux@arm.linux.org.uk,
	'Catalin Marinas' <Catalin.Marinas@arm.com>,
	'Inki Dae' <inki.dae@samsung.com>,
	linux-mm@kvack.org, 'Kyungmin Park' <kyungmin.park@samsung.com>,
	'Myungjoo Ham' <myungjoo.ham@samsung.com>,
	linux-arm-kernel@lists.infradead.org,
	'Grazvydas Ignotas' <notasas@gmail.com>
Subject: RE: [PATCH] arm: mm: lockless get_user_pages_fast
Date: Wed, 10 Apr 2013 18:10:18 +0900	[thread overview]
Message-ID: <00bc01ce35cb$38b9ffb0$aa2dff10$@samsusng.com> (raw)
In-Reply-To: <20130410082059.GA12296@e103986-lin>

> From: Steve Capper [mailto:steve.capper@arm.com]
> Sent: Wednesday, April 10, 2013 5:21 PM
> To: Chanho Park
> Cc: Steve Capper; 'Chanho Park'; linux@arm.linux.org.uk; Catalin Marinas;
> 'Inki Dae'; linux-mm@kvack.org; 'Kyungmin Park'; 'Myungjoo Ham'; linux-
> arm-kernel@lists.infradead.org; 'Grazvydas Ignotas'
> Subject: Re: [PATCH] arm: mm: lockless get_user_pages_fast
> 
> On Wed, Apr 10, 2013 at 08:30:54AM +0100, Chanho Park wrote:
> > > Apologies for the tardy response, this patch slipped past me.
> >
> > Never mind.
> >
> > > 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.
> > OK. I'll fix it.
> >
> > >
> > > 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.
> >
> > I'll add the __get_user_pages_fast implementation. BTW, HugeTLB on ARM
> > wasn't supported yet. There is no problem to add gup_huge_pmd. But I
> > think it need a test for hugepages.
> >
> 
> Thanks, that would be helpful. My plan was to then put the huge page
> specific bits in, with another patch. That way I can test it all out here.

Can I see the patch? I think it will be helpful to implement the
gup_huge_pmd.
Or how about you think except gup_huge_pmd in this patch?
IMO it will be added easily after hugetlb on arm is merged.

> 
> > > 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.
> >
> > Thanks for your suggestion.
> > I'll prepare the v2 patch.
> >
> 
> Also, just one more thing. In your gup_pte_range function there is an
> smp_rmb() just after the pte is dereferenced. I don't understand why
> though?

I think it would be needed for 64 bit machine. A pte of 64bit machine
consists of low and high value. In this version, there is no need to add it.
I'll remove it. Thanks.

Best regards,
Chanho Park

--
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>

  reply	other threads:[~2013-04-10  9:10 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
2013-04-10  7:30   ` Chanho Park
2013-04-10  8:21     ` Steve Capper
2013-04-10  9:10       ` Chanho Park [this message]
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='00bc01ce35cb$38b9ffb0$aa2dff10$@samsusng.com' \
    --to=chanho61.park@samsusng.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 \
    --cc=steve.capper@arm.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).