From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jack Steiner <steiner@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Christoph Hellwig <hch@infradead.org>,
cl@linux-foundation.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
holt@sgi.com, andrea@qumranet.com, linux-mm@kvack.org
Subject: Re: [patch 12/13] GRU Driver V3 - export is_uv_system(), zap_page_range() & follow_page()
Date: Fri, 11 Jul 2008 13:30:01 +1000 [thread overview]
Message-ID: <200807111330.02090.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080710172036.GB5972@sgi.com>
On Friday 11 July 2008 03:20, Jack Steiner wrote:
> On Fri, Jul 11, 2008 at 02:52:00AM +1000, Nick Piggin wrote:
> > lockless gup checks for struct page by checking a bit in the pte.
> > This should be enough to guarantee it is cacheable memory (unless
> > another driver has done something tricky like set the the page's
> > cache attributes to UC or WC -- I don't know if there is a way to
> > completely avoid all corner cases).
>
> The GRU itself has no need to reference the page struct.
> However, it WILL reference valid ptes that represent pages imported from
> other SSIs via xpmem. These will have cacheable ptes but no page structs.
Oh, I'm sorry Jack, I misread the patch and thought you still had
the page_to_phys thing in there... OK, then it probably isn't
broken. And in which case you would have to add a little code to
gup.c...
> Maybe checking the pte attributes is the best way to do the check.
>
> If we take this approach, what is a good API for the gup.c walker?
> Return the pte attributes?
>
> int get_user_pte(struct mm_struct *mm, unsigned long address,
> int write, unsigned long *paddr, int *pageshift, pgprot_t *prot)
>
> The GRU would enforce the check for cacheable access.
Yeah that wouldn't be a bad API, although being a lockless, may-fail,
not available on all archs kind of thing, I would prefer a different
name, maybe get_user_pte_fast() to match?
Thanks,
Nick
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jack Steiner <steiner@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Christoph Hellwig <hch@infradead.org>,
cl@linux-foundation.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
holt@sgi.com, andrea@qumranet.com, linux-mm@kvack.org
Subject: Re: [patch 12/13] GRU Driver V3 - export is_uv_system(), zap_page_range() & follow_page()
Date: Fri, 11 Jul 2008 13:30:01 +1000 [thread overview]
Message-ID: <200807111330.02090.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080710172036.GB5972@sgi.com>
On Friday 11 July 2008 03:20, Jack Steiner wrote:
> On Fri, Jul 11, 2008 at 02:52:00AM +1000, Nick Piggin wrote:
> > lockless gup checks for struct page by checking a bit in the pte.
> > This should be enough to guarantee it is cacheable memory (unless
> > another driver has done something tricky like set the the page's
> > cache attributes to UC or WC -- I don't know if there is a way to
> > completely avoid all corner cases).
>
> The GRU itself has no need to reference the page struct.
> However, it WILL reference valid ptes that represent pages imported from
> other SSIs via xpmem. These will have cacheable ptes but no page structs.
Oh, I'm sorry Jack, I misread the patch and thought you still had
the page_to_phys thing in there... OK, then it probably isn't
broken. And in which case you would have to add a little code to
gup.c...
> Maybe checking the pte attributes is the best way to do the check.
>
> If we take this approach, what is a good API for the gup.c walker?
> Return the pte attributes?
>
> int get_user_pte(struct mm_struct *mm, unsigned long address,
> int write, unsigned long *paddr, int *pageshift, pgprot_t *prot)
>
> The GRU would enforce the check for cacheable access.
Yeah that wouldn't be a bad API, although being a lockless, may-fail,
not available on all archs kind of thing, I would prefer a different
name, maybe get_user_pte_fast() to match?
Thanks,
Nick
--
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:[~2008-07-11 3:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 21:33 [patch 00/13] GRU Driver V3 - Overview steiner
2008-07-03 21:33 ` [patch 01/13] GRU Driver V3 - hardware data structures steiner
2008-07-03 21:33 ` [patch 02/13] GRU Driver V3 - GRU instructions & macros steiner
2008-07-03 21:33 ` [patch 03/13] GRU Driver V3 - driver internal header files steiner
2008-07-03 21:33 ` [patch 04/13] GRU Driver V3 - kernel services " steiner
2008-07-03 21:33 ` [patch 05/13] GRU Driver V3 - driver initialization, file & vma ops steiner
2008-07-03 21:33 ` [patch 06/13] GRU Driver V3 - page faults & exceptions steiner
2008-07-03 21:33 ` [patch 07/13] GRU Driver V3 - kernel services provide by driver steiner
2008-07-03 21:33 ` [patch 08/13] GRU Driver V3 - resource management steiner
2008-07-03 21:33 ` [patch 09/13] GRU Driver V3 - /proc interfaces steiner
2008-07-03 21:33 ` [patch 10/13] GRU Driver V3 - TLB flushing, MMUOPS callouts steiner
2008-07-03 21:33 ` [patch 11/13] GRU Driver V3 - driver makefile steiner
2008-07-03 21:34 ` [patch 12/13] GRU Driver V3 - export is_uv_system(), zap_page_range() & follow_page() steiner
2008-07-04 7:39 ` Christoph Hellwig
2008-07-07 14:39 ` Jack Steiner
2008-07-07 14:39 ` Jack Steiner
2008-07-07 14:54 ` Andrea Arcangeli
2008-07-07 14:54 ` Andrea Arcangeli
2008-07-07 16:29 ` Hugh Dickins
2008-07-07 16:29 ` Hugh Dickins
2008-07-07 16:53 ` Jack Steiner
2008-07-07 16:53 ` Jack Steiner
2008-07-08 2:16 ` Nick Piggin
2008-07-08 2:16 ` Nick Piggin
2008-07-09 19:11 ` Jack Steiner
2008-07-09 19:11 ` Jack Steiner
2008-07-10 7:31 ` Nick Piggin
2008-07-10 7:31 ` Nick Piggin
2008-07-10 13:29 ` Jack Steiner
2008-07-10 13:29 ` Jack Steiner
2008-07-10 14:21 ` Nick Piggin
2008-07-10 14:21 ` Nick Piggin
2008-07-10 16:33 ` Jack Steiner
2008-07-10 16:33 ` Jack Steiner
2008-07-10 16:52 ` Nick Piggin
2008-07-10 16:52 ` Nick Piggin
2008-07-10 17:20 ` Jack Steiner
2008-07-10 17:20 ` Jack Steiner
2008-07-11 3:30 ` Nick Piggin [this message]
2008-07-11 3:30 ` Nick Piggin
2008-07-07 18:58 ` Arjan van de Ven
2008-07-07 18:58 ` Arjan van de Ven
2008-07-07 19:29 ` Jack Steiner
2008-07-07 19:29 ` Jack Steiner
2008-07-07 21:03 ` Andrea Arcangeli
2008-07-07 21:03 ` Andrea Arcangeli
2008-07-07 14:45 ` Christoph Lameter
2008-07-07 17:58 ` Jack Steiner
2008-07-07 17:58 ` Jack Steiner
2008-07-03 21:34 ` [patch 13/13] GRU Driver V3 - driver/misc Makefile & Kconfig changes steiner
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=200807111330.02090.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=andrea@qumranet.com \
--cc=cl@linux-foundation.org \
--cc=hch@infradead.org \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.