From: Brandon Niemczyk <brandon@snprogramming.com>
To: multisyncfe991@hotmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: About a change to the implementation of spin lock in 2.6.12 kernel.
Date: Thu, 14 Jul 2005 12:26:38 -0400 [thread overview]
Message-ID: <1121358399.4685.9.camel@localhost> (raw)
In-Reply-To: <BAY108-DAV7F3CC1BA8D84C5323469193D10@phx.gbl>
On Thu, 2005-07-14 at 09:21 -0700, multisyncfe991@hotmail.com wrote:
> Hi Willy,
>
> I think at least I can remove the LOCK instruction when the lock is already
> held by someone else and enter the spinning wait directly, right?
If the lock is already held by someone else, the cpu is just going to
burn cycles until it's not. So why do you care?
--
Brandon Niemczyk
next prev parent reply other threads:[~2005-07-14 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 2:20 About a change to the implementation of spin lock in 2.6.12 kernel multisyncfe991
2005-07-14 5:16 ` Willy Tarreau
2005-07-14 16:21 ` multisyncfe991
2005-07-14 16:26 ` Brandon Niemczyk [this message]
2005-11-09 17:57 ` Does Printk() block another CPU in dual cpu platforms? John Smith
2005-11-10 3:31 ` Fawad Lateef
2005-07-15 19:22 ` Volatile vs Non-Volatile Spin Locks on SMP multisyncfe991
2005-07-17 12:51 ` Joe Seigh
2005-07-18 13:40 ` Joe Seigh
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=1121358399.4685.9.camel@localhost \
--to=brandon@snprogramming.com \
--cc=linux-kernel@vger.kernel.org \
--cc=multisyncfe991@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox