From: Richard Henderson <rth@twiddle.net>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH][2.5] Protect smp_call_function_data w/ spinlocks on Alpha
Date: Mon, 17 Feb 2003 00:15:44 -0800 [thread overview]
Message-ID: <20030217001544.A13101@twiddle.net> (raw)
In-Reply-To: <Pine.LNX.4.50.0302141158070.3518-100000@montezuma.mastecende.com>; from zwane@holomorphy.com on Fri, Feb 14, 2003 at 12:16:12PM -0500
On Fri, Feb 14, 2003 at 12:16:12PM -0500, Zwane Mwaikambo wrote:
> Ok the reason being is that the lock not only protects the
> smp_call_function_data pointer but also acts as a lock for that critical
> section. Without it you'll constantly be overwriting the pointer halfway
> through IPI acceptance (or even worse whilst a remote CPU is assigning the
> data members).
Really. Show me the sequence there?
I happen to like the pointer_lock a lot, and think we should
make more use of it on systems known to have cmpxchg. It
saves on the number of cache lines that have to get bounced
between processors.
r~
next prev parent reply other threads:[~2003-02-17 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 11:51 [PATCH][2.5] Protect smp_call_function_data w/ spinlocks on Alpha Zwane Mwaikambo
2003-02-14 14:53 ` Ivan Kokshaysky
2003-02-14 17:16 ` Zwane Mwaikambo
2003-02-17 8:15 ` Richard Henderson [this message]
2003-02-17 8:32 ` Zwane Mwaikambo
2003-02-17 14:23 ` Ivan Kokshaysky
2003-02-17 14:31 ` Zwane Mwaikambo
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=20030217001544.A13101@twiddle.net \
--to=rth@twiddle.net \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zwane@holomorphy.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.