From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, akpm@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] v1 expedited "big hammer" RCU grace periods
Date: Thu, 23 Apr 2009 08:47:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904230842571.3101@localhost.localdomain> (raw)
In-Reply-To: <20090423153402.GC6877@linux.vnet.ibm.com>
On Thu, 23 Apr 2009, Paul E. McKenney wrote:
>
> Hmmm... I need to ask Jeff Chua what HZ he was running with. Because if
> there was some read-side critical section soaking up 30 milliseconds,
> all that hammering will do is slow things down...
The original bug report comes from simply bootup:
"I'm loading all the firewall rules during boot-up and this 6 secs
slowness is really not very nice to wait for."
IOW, the problematic case likely effectively has _nothing_ else going on.
Sure, there might be some parallelism (the bootup scripts are getting
better for that), but hopefully not 6 seconds worth, and not likely any
complex critical sections.
Linus
next prev parent reply other threads:[~2009-04-23 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 5:25 [PATCH RFC] v1 expedited "big hammer" RCU grace periods Paul E. McKenney
2009-04-23 6:11 ` Lai Jiangshan
2009-04-23 15:15 ` Paul E. McKenney
2009-04-24 0:39 ` Lai Jiangshan
2009-04-24 1:13 ` Paul E. McKenney
2009-04-23 7:54 ` Ingo Molnar
2009-04-23 15:34 ` Paul E. McKenney
2009-04-23 15:47 ` Linus Torvalds [this message]
2009-04-23 18:29 ` Paul E. McKenney
2009-04-23 13:45 ` Mathieu Desnoyers
2009-04-23 16:54 ` 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=alpine.LFD.2.00.0904230842571.3101@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--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=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=r000n@r000n.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox