From: Darren Hart <dvhltc@us.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Chris Friesen <cfriesen@nortel.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, josh@joshtriplett.org, niv@us.ibm.com,
tglx@linutronix.de, peterz@infradead.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: Re: [RFC patch] introduce sys_membarrier(): process-wide memory barrier (v9)
Date: Wed, 24 Feb 2010 09:29:46 -0800 [thread overview]
Message-ID: <4B85620A.7000901@us.ibm.com> (raw)
In-Reply-To: <20100224091052.GY9738@laptop>
Nick Piggin wrote:
> When writing multiprocessor scalable software, threads should often be
> avoided. They share so much state that it is easy to run into
> scalability issues in the kernel. So yes it would be really nice to
> have userspace RCU available in a process-shared mode.
A bit off topic, but I'm interested in what you feel some of these
scalability issues are. Is it mostly bouncing this shared context from
one CPU to the next and the related cache effects, or is there something
more you are referring to?
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next prev parent reply other threads:[~2010-02-24 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 22:46 [RFC patch] introduce sys_membarrier(): process-wide memory barrier (v9) Mathieu Desnoyers
2010-02-12 22:46 ` Mathieu Desnoyers
2010-02-15 19:59 ` Paul E. McKenney
2010-02-16 0:57 ` KOSAKI Motohiro
2010-02-22 18:38 ` Chris Friesen
2010-02-22 21:23 ` Mathieu Desnoyers
2010-02-24 9:10 ` Nick Piggin
2010-02-24 15:22 ` Mathieu Desnoyers
2010-02-25 5:33 ` Nick Piggin
2010-02-25 16:53 ` Mathieu Desnoyers
2010-02-25 17:25 ` Steven Rostedt
2010-02-25 17:51 ` Mathieu Desnoyers
2010-02-25 18:00 ` Mathieu Desnoyers
2010-02-25 18:20 ` Add this to tip (was: Re: [RFC patch] introduce sys_membarrier(): process-wide memory barrier (v9)) Steven Rostedt
2010-02-25 18:08 ` [RFC patch] introduce sys_membarrier(): process-wide memory barrier (v9) Steven Rostedt
2010-02-26 5:08 ` Nick Piggin
2010-02-26 5:37 ` Steven Rostedt
2010-02-24 17:29 ` Darren Hart [this message]
2010-02-25 5:22 ` Nick Piggin
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=4B85620A.7000901@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=cfriesen@nortel.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=josh@joshtriplett.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=nmiell@comcast.net \
--cc=npiggin@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).