From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Paul Jackson <pj@sgi.com>
Cc: ego@in.ibm.com, mingo@elte.hu, nickpiggin@yahoo.com.au,
arjan@infradead.org, rusty@rustcorp.com.au, torvalds@osdl.org,
akpm@osdl.org, linux-kernel@vger.kernel.org,
arjan@intel.linux.com, davej@redhat.com, dipankar@in.ibm.com,
vatsa@in.ibm.com, ashok.raj@intel.com
Subject: Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug
Date: Wed, 30 Aug 2006 08:14:05 -0700 [thread overview]
Message-ID: <20060830151405.GD1296@us.ibm.com> (raw)
In-Reply-To: <20060829193828.d38395fe.pj@sgi.com>
On Tue, Aug 29, 2006 at 07:38:28PM -0700, Paul Jackson wrote:
> Paul E. McKenney wrote:
> > Let me throw something together...
>
> I think it's the hotplug folks that were most interested
> in this "unfair rwsem" lock, for lock_cpu_hotplug().
Yep, been chatting with them separately.
> I wouldn't spend any effort on throwing this together
> just for cpusets. I'm not looking to change cpuset
> locking anytime soon.
Well, my next question was going to be whether cpuset readers really
need to exclude the writers, or whether there can be a transition
period while the mastodon makes the change as long as it avoids stomping
the locusts. ;-)
Thanx, Paul
next prev parent reply other threads:[~2006-08-30 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 10:34 [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug Gautham R Shenoy
2006-08-24 11:00 ` Arjan van de Ven
2006-08-24 14:03 ` Gautham R Shenoy
2006-08-24 14:16 ` Arjan van de Ven
2006-08-24 14:55 ` Nick Piggin
2006-08-24 15:00 ` Ingo Molnar
2006-08-24 15:53 ` Nick Piggin
2006-08-25 3:53 ` Gautham R Shenoy
2006-08-27 7:59 ` Paul Jackson
2006-08-27 8:42 ` Keith Owens
2006-08-27 9:10 ` Paul Jackson
2006-08-29 18:05 ` Paul E. McKenney
2006-08-29 19:31 ` Paul Jackson
2006-08-29 20:03 ` Paul E. McKenney
2006-08-30 2:38 ` Paul Jackson
2006-08-30 15:14 ` Paul E. McKenney [this message]
2006-08-30 17:54 ` Paul Jackson
2006-08-30 18:13 ` 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=20060830151405.GD1296@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=arjan@intel.linux.com \
--cc=ashok.raj@intel.com \
--cc=davej@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=vatsa@in.ibm.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.