All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, davem@davemloft.net,
	dada1@cosmosbay.com, zbr@ioremap.net, jeff.chua.linux@gmail.com,
	paulus@samba.org, laijs@cn.fujitsu.com, jengelh@medozas.de,
	r000n@r000n.net, benh@kernel.crashing.org,
	mathieu.desnoyers@polymtl.ca
Subject: Re: [PATCH RFC] v5 expedited "big hammer" RCU grace periods
Date: Mon, 18 May 2009 09:02:54 -0700	[thread overview]
Message-ID: <20090518160254.GD6768@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090518154241.GA27047@elte.hu>

On Mon, May 18, 2009 at 05:42:41PM +0200, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > > i might be missing something fundamental here, but why not just 
> > > have per CPU helper threads, all on the same waitqueue, and wake 
> > > them up via a single wake_up() call? That would remove the SMP 
> > > cross call (wakeups do immediate cross-calls already).
> > 
> > My concern with this is that the cache misses accessing all the 
> > processes on this single waitqueue would be serialized, slowing 
> > things down. In contrast, the bitmask that smp_call_function() 
> > traverses delivers on the order of a thousand CPUs' worth of bits 
> > per cache miss.  I will give it a try, though.
> 
> At least if you go via the migration threads, you can queue up 
> requests to them locally. But there's going to be cachemisses 
> _anyway_, since you have to access them all from a single CPU, and 
> then they have to fetch details about what to do, and then have to 
> notify the originator about completion.

Ah, so you are suggesting that I use smp_call_function() to run code on
each CPU that wakes up that CPU's migration thread?  I will take a look
at this.

							Thanx, Paul

  reply	other threads:[~2009-05-18 16:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17 19:11 [PATCH RFC] v5 expedited "big hammer" RCU grace periods Paul E. McKenney
2009-05-17 20:02 ` Evgeniy Polyakov
2009-05-17 22:08   ` Paul E. McKenney
2009-05-18  6:59 ` Lai Jiangshan
2009-05-18 14:40   ` Paul E. McKenney
2009-05-18  7:56 ` Ingo Molnar
2009-05-18 15:14   ` Paul E. McKenney
2009-05-18 15:42     ` Ingo Molnar
2009-05-18 16:02       ` Paul E. McKenney [this message]
2009-05-19  8:58         ` Ingo Molnar
2009-05-19 12:33           ` Paul E. McKenney
2009-05-19 12:44             ` Ingo Molnar
2009-05-19 16:18               ` Paul E. McKenney
2009-05-20  8:09                 ` Ingo Molnar
2009-05-20 15:30                   ` Paul E. McKenney
2009-05-27 22:57                     ` Ingo Molnar
2009-05-29  1:22                       ` Paul E. McKenney
2009-05-29 12:06                         ` Gautham R Shenoy
2009-05-30  4:56                           ` Paul E. McKenney

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=20090518160254.GD6768@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=jeff.chua.linux@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=r000n@r000n.net \
    --cc=torvalds@linux-foundation.org \
    --cc=zbr@ioremap.net \
    /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.