linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: aneesh.kumar@linux.vnet.ibm.com (Aneesh Kumar K.V)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/6] mm: Introduce a general RCU get_user_pages_fast.
Date: Mon, 13 Oct 2014 10:45:24 +0530	[thread overview]
Message-ID: <87d29w1rf7.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141002121902.GA2342@redhat.com>

Andrea Arcangeli <aarcange@redhat.com> writes:

> Hi Steve,
>
> On Fri, Sep 26, 2014 at 03:03:48PM +0100, Steve Capper wrote:
>> This patch provides a general RCU implementation of get_user_pages_fast
>> that can be used by architectures that perform hardware broadcast of
>> TLB invalidations.
>> 
>> It is based heavily on the PowerPC implementation by Nick Piggin.
>
> It'd be nice if you could also at the same time apply it to sparc and
> powerpc in this same patchset to show the effectiveness of having a
> generic version. Because if it's not a trivial drop-in replacement,
> then this should go in arch/arm* instead of mm/gup.c...

on ppc64 we have one challenge, we do need to support hugepd. At the pmd
level we can have hugepte, normal pmd pointer or a pointer to hugepage
directory which is used in case of some sub-architectures/platforms. ie,
the below part of gup implementation in ppc64

else if (is_hugepd(pmdp)) {
	if (!gup_hugepd((hugepd_t *)pmdp, PMD_SHIFT,
			addr, next, write, pages, nr))
		return 0;


-aneesh

  parent reply	other threads:[~2014-10-13  5:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 14:03 [PATCH V4 0/6] RCU get_user_pages_fast and __get_user_pages_fast Steve Capper
2014-09-26 14:03 ` [PATCH V4 1/6] mm: Introduce a general RCU get_user_pages_fast Steve Capper
2014-09-29 21:51   ` Hugh Dickins
2014-10-01 11:11     ` Catalin Marinas
2014-10-02 16:00     ` Steve Capper
2014-10-02 12:19   ` Andrea Arcangeli
2014-10-02 16:18     ` Steve Capper
2014-10-02 16:54       ` Andrea Arcangeli
2014-10-13  5:15     ` Aneesh Kumar K.V [this message]
2014-10-13  5:21       ` David Miller
2014-10-13 11:44         ` Steve Capper
2014-10-13 16:06           ` David Miller
2014-10-14 12:38             ` Steve Capper
2014-10-14 16:30               ` David Miller
2014-10-13 17:04           ` Aneesh Kumar K.V
2014-10-13  6:22   ` Aneesh Kumar K.V
2014-09-26 14:03 ` [PATCH V4 2/6] arm: mm: Introduce special ptes for LPAE Steve Capper
2014-09-26 14:03 ` [PATCH V4 3/6] arm: mm: Enable HAVE_RCU_TABLE_FREE logic Steve Capper
2014-09-26 14:03 ` [PATCH V4 4/6] arm: mm: Enable RCU fast_gup Steve Capper
2014-09-26 14:03 ` [PATCH V4 5/6] arm64: mm: Enable HAVE_RCU_TABLE_FREE logic Steve Capper
2014-09-26 14:03 ` [PATCH V4 6/6] arm64: mm: Enable RCU fast_gup Steve Capper
2015-02-27 12:42 ` [PATCH V4 0/6] RCU get_user_pages_fast and __get_user_pages_fast Jon Masters
2015-02-27 13:20   ` Mark Rutland
2015-03-02 14:16     ` Mark Rutland
     [not found]   ` <54F3C6AD.50300@redhat.com>
2015-03-02  5:58     ` PMD update corruption (sync question) Jon Masters
2015-03-02 10:50       ` Catalin Marinas
2015-03-02 11:06         ` Jon Masters
2015-03-02 12:31           ` Peter Zijlstra
2015-03-02 12:40             ` Geert Uytterhoeven
2015-03-02 22:21         ` Jon Masters
2015-03-02 22:29           ` Jon Masters
2015-03-03  9:06           ` Arnd Bergmann
2015-03-03 15:46             ` Jon Masters

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=87d29w1rf7.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.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).