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 09:27:39 +1100 [thread overview]
Message-ID: <1197584859.15741.185.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0712131332100.24778@schroedinger.engr.sgi.com>
On Thu, 2007-12-13 at 13:33 -0800, Christoph Lameter wrote:
> >
> > Ah ok, so that's a NUMA issue due to how the quicklists are
> implemented,
> > I see. Note that the flush isn't necessary a solution on all
> platforms.
> > On powerpc, I -still- need to defer with RCU as we don't do anything
> in
> > flush tlb. Our TLB invalidations are HW broadcast in the first
> place,
> > but what we need to sync with is the SW hash reload code.
> >
> > So your solution in the quicklists doesn't solve the problem for us.
>
> No this may mean that the problem does not exist on powerpc since it
> seems to be okay to free pages before all processors have flushed the
> TLBs? Or are you deferrring the freeing of the pages via RCU?
I'm deferring the freeing with RCU.
Ben.
next prev parent reply other threads:[~2007-12-13 22:29 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 [this message]
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
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=1197584859.15741.185.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 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.