From: Dave Hansen <haveblue@us.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ken Chen <kenchen@google.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Badari Pulavarty <pbadari@gmail.com>,
linux-mm <linux-mm@kvack.org>,
tony.luck@intel.com
Subject: Re: [rfc] lockless get_user_pages for dio (and more)
Date: Mon, 15 Oct 2007 17:14:47 -0700 [thread overview]
Message-ID: <1192493687.6118.138.camel@localhost> (raw)
In-Reply-To: <200710161215.33284.nickpiggin@yahoo.com.au>
> +static int gup_pte_range(pmd_t pmd, unsigned long addr, unsigned long end, int write, struct page **pages, int *nr)
> +{
> + pte_t *ptep;
> +
> + /* XXX: this won't work for 32-bit (must map pte) */
> + ptep = (pte_t *)pmd_page_vaddr(pmd) + pte_index(addr);
> + do {
> + pte_t pte = *ptep;
> + unsigned long pfn;
> + struct page *page;
> +
> + if ((pte_val(pte) & (_PAGE_PRESENT|_PAGE_USER)) != (_PAGE_PRESENT|_PAGE_USER))
> + return 0;
> +
> + if (write && !pte_write(pte))
> + return 0;
> +
> + /* XXX: really need new bit in pte to denote normal page */
> + pfn = pte_pfn(pte);
> + if (unlikely(!pfn_valid(pfn)))
> + return 0;
Is that little pfn_valid() nugget to help detect VM_IO and VM_PFNMAP
areas? Does that work 100% of the time? Is it for anything else?
If that is all that you want a bit in the pte for, I guess we could get
a bitfield or a simple flag in the mm to say whether there are any
VM_IO/PFNMAP areas around. If we used the same IPI/RCU rules as
pagetables to manage such a flag, I think it would be sufficient to dump
us into the slow path when we hit those areas.
-- Dave
--
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:[~2007-10-16 0:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 22:52 [rfc] more granular page table lock for hugepages Siddha, Suresh B
2007-10-09 20:23 ` Ken Chen
2007-10-09 21:05 ` Badari Pulavarty
2007-10-10 0:15 ` Siddha, Suresh B
2007-10-10 6:10 ` Ken Chen
2007-10-10 7:50 ` Ken Chen
2007-10-11 11:39 ` Nick Piggin
2007-10-12 20:34 ` Siddha, Suresh B
2007-10-13 23:27 ` Nick Piggin
2007-10-14 1:01 ` [rfc] lockless get_user_pages for dio (and more) Nick Piggin
2007-10-14 18:19 ` Siddha, Suresh B
2007-10-15 4:15 ` Nick Piggin
2007-10-15 12:25 ` Nick Piggin
2007-10-15 17:03 ` Badari Pulavarty
2007-10-15 17:49 ` Siddha, Suresh B
2007-10-15 17:54 ` Siddha, Suresh B
2007-10-15 20:21 ` Ken Chen
2007-10-16 2:15 ` Nick Piggin
2007-10-16 0:14 ` Dave Hansen [this message]
2007-10-16 3:26 ` Nick Piggin
2007-10-16 3:32 ` Nick Piggin
2007-12-10 21:30 ` Dave Kleikamp
2007-12-12 4:57 ` Nick Piggin
2007-12-12 5:11 ` Dave Kleikamp
2007-12-12 5:40 ` Nick Piggin
2008-01-16 19:58 ` Dave Kleikamp
2008-01-17 6:34 ` Nick Piggin
2008-01-24 7:06 ` Nick Piggin
2007-10-14 15:42 ` [rfc] more granular page table lock for hugepages Siddha, Suresh B
2007-10-15 4:17 ` 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=1192493687.6118.138.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=kenchen@google.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pbadari@gmail.com \
--cc=suresh.b.siddha@intel.com \
--cc=tony.luck@intel.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