From: Stephen Hemminger <shemminger@osdl.org>
To: john moser <bluefoxicy@linux.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: spin_lock() and smp/multicall logic
Date: Thu, 08 Jan 2004 20:50:54 -0800 [thread overview]
Message-ID: <3FFE332E.7070307@osdl.org> (raw)
In-Reply-To: <20040109003522.F1411E4B9@sitemail.everyone.net>
john moser wrote:
> As always, CC all replies back to me.
>
> I'm looking at include/linux/spinlock.h and I'm incredibly confused on something.
Buggy implementation of run_once deleted
> SO the two questions I'd like to address here are:
>
> 1) What is the purpose of spin_lock()
> 2) Am I the first person to come up with this method of non-parallel execution
> guarentee?
You invented an unsafe version of monitor using spin-locks.
Go read a on SMP operating systems.
"UNIX(R) Systems for Modern Architectures: Symmetric Multiprocessing and
Caching for Kernel Programmers"
prev parent reply other threads:[~2004-01-09 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 0:35 spin_lock() and smp/multicall logic john moser
2004-01-09 4:50 ` Stephen Hemminger [this message]
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=3FFE332E.7070307@osdl.org \
--to=shemminger@osdl.org \
--cc=bluefoxicy@linux.net \
--cc=linux-kernel@vger.kernel.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