From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Christoph Lameter' <clameter@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>, Andi Kleen <ak@suse.de>,
Zoltan Menyhart <Zoltan.Menyhart@bull.net>,
linux-mm@kvack.org, Zoltan.Menyhart@free.fr,
linux-i64@vger.kernel.org
Subject: RE: RFC: RCU protected page table walking
Date: Wed, 3 May 2006 19:51:36 -0700 [thread overview]
Message-ID: <4t16i2$tp1jo@orsmga001.jf.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605031649400.32117@schroedinger.engr.sgi.com>
Christoph Lameter wrote on Wednesday, May 03, 2006 4:54 PM
> On Wed, 3 May 2006, Hugh Dickins wrote:
> > Those architectures (including i386 and x86_64) which #define their
> > __pte_free_tlb etc. to tlb_remove_page are safe as is. But Zoltan's
> > ia64 #defines it to pte_free, which looks like it may free_page before
> > the TLB flush. But it is surprising if it has actually been unsafe
>
> Sorry but I am in .au right now with spotty high latency connectivity.
> But the people on linux-ia64 should know. Ken?
A while back ia64 reinstated per-cpu pgtable quicklist, which bypasses tlb_gather/tlb_finish_mmu for page table pages. It should be
safe AFAICT
because TLB for user address and vhpt are already flushed by the time
pte_free_tlb() is called.
--
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:[~2006-05-04 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 15:31 RFC: RCU protected page table walking Zoltan Menyhart
2006-05-03 16:46 ` Andi Kleen
2006-05-03 18:00 ` Hugh Dickins
2006-05-03 23:54 ` Christoph Lameter
2006-05-03 23:54 ` Christoph Lameter
2006-05-04 2:51 ` Chen, Kenneth W [this message]
2006-05-04 4:28 ` Hugh Dickins
2006-05-04 9:26 ` Zoltan Menyhart
2006-05-04 9:31 ` Andi Kleen
2006-05-04 11:32 ` Zoltan Menyhart
2006-05-04 12:00 ` Andi Kleen
2006-05-04 13:13 ` Robin Holt
2006-05-04 13:54 ` Zoltan Menyhart
2006-05-04 15:27 ` Hugh Dickins
2006-05-04 15:27 ` Hugh Dickins
2006-05-04 9:19 ` Zoltan Menyhart
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='4t16i2$tp1jo@orsmga001.jf.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=Zoltan.Menyhart@bull.net \
--cc=Zoltan.Menyhart@free.fr \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-i64@vger.kernel.org \
--cc=linux-mm@kvack.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 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.