From: Oleg Nesterov <oleg@tv-sign.ru>
To: Nick Piggin <npiggin@suse.de>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
Ingo Molnar <mingo@elte.hu>,
Nikita Danilov <nikita@clusterfs.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] queued spinlocks (i386)
Date: Thu, 29 Mar 2007 22:42:13 +0400 [thread overview]
Message-ID: <20070329184213.GA83@tv-sign.ru> (raw)
In-Reply-To: <20070328070459.GC12508@wotan.suse.de>
On 03/28, Nick Piggin wrote:
>
> Well with my queued spinlocks, all that lockbreak stuff can just come out
> of the spin_lock, break_lock out of the spinlock structure, and
> need_lockbreak just becomes (lock->qhead - lock->qtail > 1).
Q: queued spinlocks are not CONFIG_PREEMPT friendly,
> + asm volatile(LOCK_PREFIX "xaddw %0, %1\n\t"
> + : "+r" (pos), "+m" (lock->qhead) : : "memory");
> + while (unlikely(pos != lock->qtail))
> + cpu_relax();
once we incremented lock->qhead, we have no optiion but should spin with
preemption disabled until pos == lock->qtail, yes?
Oleg.
next prev parent reply other threads:[~2007-03-29 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 15:54 Oleg Nesterov
2007-03-27 15:22 ` Andi Kleen
2007-03-28 7:04 ` Nick Piggin
2007-03-29 18:42 ` Oleg Nesterov [this message]
2007-03-29 22:16 ` Davide Libenzi
2007-03-30 2:06 ` Lee Revell
2007-03-30 2:17 ` Nick Piggin
2007-03-30 4:44 ` Lee Revell
2007-03-30 1:53 ` 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=20070329184213.GA83@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikita@clusterfs.com \
--cc=npiggin@suse.de \
/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
Powered by JetHome