From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
axboe@kernel.dk, linux-mm@kvack.org, linux-arch@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [patch 2/2]: introduce fast_gup
Date: Wed, 14 May 2008 13:33:14 -0500 [thread overview]
Message-ID: <1210789994.6377.21.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <20080422094629.GC23770@wotan.suse.de>
On Tue, 2008-04-22 at 11:46 +0200, Nick Piggin wrote:
> On Tue, Apr 22, 2008 at 11:42:36AM +0200, Peter Zijlstra wrote:
> > On Fri, 2008-03-28 at 04:00 +0100, Nick Piggin wrote:
> >
> > > +static noinline int gup_pte_range(pmd_t pmd, unsigned long addr,
> > > + unsigned long end, int write, struct page **pages, int *nr)
> > > +{
> > > + unsigned long mask, result;
> > > + pte_t *ptep;
> > > +
> > > + result = _PAGE_PRESENT|_PAGE_USER;
> > > + if (write)
> > > + result |= _PAGE_RW;
> > > + mask = result | _PAGE_SPECIAL;
> > > +
> > > + ptep = pte_offset_map(&pmd, addr);
> > > + do {
> > > + /*
> > > + * XXX: careful. On 3-level 32-bit, the pte is 64 bits, and
> > > + * we need to make sure we load the low word first, then the
> > > + * high. This means _PAGE_PRESENT should be clear if the high
> > > + * word was not valid. Currently, the C compiler can issue
> > > + * the loads in any order, and I don't know of a wrapper
> > > + * function that will do this properly, so it is broken on
> > > + * 32-bit 3-level for the moment.
> > > + */
> > > + pte_t pte = *ptep;
> > > + struct page *page;
> > > +
> > > + if ((pte_val(pte) & mask) != result)
> > > + return 0;
> >
> > This return path fails to unmap the pmd.
>
> Ah good catch. As you can see I haven't done any highmem testing ;)
> Which I will do so before sending upstream.
Which will be when? We'd really like to see this in mainline as soon as
possible and in -mm in the meanwhile.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
--
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-05-14 18:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 2:54 [patch 0/2]: lockless get_user_pages patchset Nick Piggin
2008-03-28 2:55 ` [patch 1/2]: x86: implement pte_special Nick Piggin
2008-03-28 3:23 ` David Miller, Nick Piggin
2008-03-28 3:31 ` Nick Piggin
2008-03-28 3:44 ` David Miller, Nick Piggin
2008-03-28 4:04 ` Nick Piggin
2008-03-28 4:09 ` David Miller, Nick Piggin
2008-03-28 4:15 ` Nick Piggin
2008-03-28 4:16 ` David Miller, Nick Piggin
2008-03-28 4:19 ` Nick Piggin
2008-03-28 4:17 ` Nick Piggin
2008-03-28 3:00 ` [patch 2/2]: introduce fast_gup Nick Piggin
2008-03-28 10:01 ` Jens Axboe
2008-04-17 15:03 ` Peter Zijlstra
2008-04-17 15:25 ` Linus Torvalds
2008-04-17 16:12 ` Peter Zijlstra
2008-04-17 16:18 ` Linus Torvalds
2008-04-17 16:35 ` Peter Zijlstra
2008-04-17 16:40 ` Linus Torvalds
2008-04-17 17:23 ` Peter Zijlstra
2008-04-17 18:28 ` Linus Torvalds
2008-04-22 3:14 ` Nick Piggin
2008-04-18 6:31 ` Geert Uytterhoeven
2008-04-18 14:40 ` Linus Torvalds
2008-04-18 9:58 ` Jeremy Fitzhardinge
2008-04-21 12:00 ` Avi Kivity
2008-04-21 12:30 ` Peter Zijlstra
2008-04-21 13:26 ` Avi Kivity
2008-04-21 14:35 ` Peter Zijlstra
2008-04-22 3:23 ` Nick Piggin
2008-04-22 7:19 ` Avi Kivity
2008-04-22 8:07 ` Ingo Molnar
2008-04-22 9:42 ` Peter Zijlstra
2008-04-22 9:46 ` Nick Piggin
2008-05-14 18:33 ` Dave Kleikamp [this message]
2008-05-15 1:13 ` Nick Piggin
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=1210789994.6377.21.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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