From: "Lee Revell" <rlrevell@joe-job.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Oleg Nesterov" <oleg@tv-sign.ru>,
"Nick Piggin" <npiggin@suse.de>,
"Ravikiran G Thirumalai" <kiran@scalex86.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Nikita Danilov" <nikita@clusterfs.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] queued spinlocks (i386)
Date: Thu, 29 Mar 2007 22:06:41 -0400 [thread overview]
Message-ID: <75b66ecd0703291906q265f9cc7g486cf65484ba8393@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703291215440.1199@alien.or.mcafeemobile.com>
On 3/29/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> On Thu, 29 Mar 2007, Oleg Nesterov wrote:
>
> > 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,
>
> Why? Is CONFIG_PREEMPT friendly to anyone? :)
Until someone fixes all the places in the kernel where scheduling can
be held off for tens of milliseconds, CONFIG_PREEMPT will be an
absolute requirement for many applications like audio and gaming.
Many of these were fixed a while back during early -rt development but
at some point the process stalled as the remaining cases were too hard
to fix...
Lee
next prev parent reply other threads:[~2007-03-30 2:06 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
2007-03-29 22:16 ` Davide Libenzi
2007-03-30 2:06 ` Lee Revell [this message]
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=75b66ecd0703291906q265f9cc7g486cf65484ba8393@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikita@clusterfs.com \
--cc=npiggin@suse.de \
--cc=oleg@tv-sign.ru \
/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
all inboxes | Powered by JetHome®