From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>,
Tony Luck <tony.luck@intel.com>,
Asit Mallick <asit.k.mallick@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: What was the problem with quicklists and x86-64?
Date: Fri, 14 Dec 2007 10:19:28 +1100 [thread overview]
Message-ID: <1197587969.15741.191.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0712131514130.29017@schroedinger.engr.sgi.com>
On Thu, 2007-12-13 at 15:14 -0800, Christoph Lameter wrote:
> On Fri, 14 Dec 2007, Benjamin Herrenschmidt wrote:
>
> > We have a separate batch to store page table pages with an RCU head on
> > it, we fire it off when it's full or when tlb gather is complete.
>
> full? You need to wait otill the tlb gather is complete.
No, we fire it off with RCU, we don't need to wait for TLB gather to be
complete. All we care about is sync with other CPUs doing a page table
walk and it's enough for us. We do -not- need to synchronize with TLB
invalidations and we don't use IPIs for those anyway.
Ben.
next prev parent reply other threads:[~2007-12-13 23:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 19:14 What was the problem with quicklists and x86-64? Jeremy Fitzhardinge
2007-12-13 19:47 ` Christoph Lameter
2007-12-13 20:47 ` Benjamin Herrenschmidt
2007-12-13 20:53 ` Christoph Lameter
2007-12-13 21:03 ` Benjamin Herrenschmidt
2007-12-13 21:33 ` Christoph Lameter
2007-12-13 22:27 ` Benjamin Herrenschmidt
2007-12-13 22:36 ` Christoph Lameter
2007-12-13 23:10 ` Benjamin Herrenschmidt
2007-12-13 23:14 ` Christoph Lameter
2007-12-13 23:19 ` Benjamin Herrenschmidt [this message]
2007-12-13 22:27 ` Siddha, Suresh B
2007-12-13 22:52 ` Christoph Lameter
2007-12-13 20:54 ` Siddha, Suresh B
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=1197587969.15741.191.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=asit.k.mallick@intel.com \
--cc=clameter@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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