From: john cooper <john.cooper@timesys.com>
To: "Bill Huey (hui)" <bhuey@lnxw.com>
Cc: Esben Nielsen <simlo@phys.au.dk>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
john cooper <john.cooper@timesys.com>
Subject: Re: Priority Inheritance Test (Real-Time Preemption)
Date: Mon, 22 Nov 2004 20:34:44 -0500 [thread overview]
Message-ID: <41A293B4.8000002@timesys.com> (raw)
In-Reply-To: <20041122213054.GB9058@nietzsche.lynx.com>
Bill Huey (hui) wrote:
> On Mon, Nov 22, 2004 at 09:16:18AM -0500, john cooper wrote:
>
>>I'd hazard a guess the reason existing implementations do not
>>do this type of dependency-chain closure is the complexity of a
>>general approach. Getting correct behavior and scaling on SMP
>>require some restrictions of how lock ownership is maintained,
>>otherwise fine grained locking is not possible. Another likely
>
>
> What do you mean by that ? Are you talking about strict priority
> obedience by the system ?
Not quite if I understand your question. I was referring to
avoiding having a global lock to synchronize the conglomerate
data structure when doing a PI dependency walk. The problem
is the lock must be acquired not only in PI scenarios but in
any case which may possibly lead to one or affect a concurrent
PI in progress.
True this global lock is mostly an issue for large count
SMP systems. But as witnessed by such voodoo[1] mechanisms
as rcu, scalability problems are real at that end of the
spectrum.
-john
[1] in a 'nice' way.
--
john.cooper@timesys.com
next prev parent reply other threads:[~2004-11-23 1:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 20:29 Priority Inheritance Test (Real-Time Preemption) Esben Nielsen
2004-11-22 0:27 ` Ingo Molnar
2004-11-23 13:34 ` Ingo Molnar
2004-11-23 15:47 ` Esben Nielsen
2004-11-23 23:03 ` Esben Nielsen
2004-11-24 3:42 ` Ingo Molnar
2004-11-24 7:51 ` Ingo Molnar
2004-11-24 8:07 ` Ingo Molnar
2004-11-24 8:33 ` Esben Nielsen
2004-11-24 9:55 ` Ingo Molnar
2004-11-24 10:18 ` Ingo Molnar
2004-11-25 15:46 ` Esben Nielsen
2004-11-25 16:58 ` Ingo Molnar
2004-11-25 16:08 ` Esben Nielsen
2004-11-25 17:14 ` Ingo Molnar
2004-11-25 22:08 ` Esben Nielsen
2004-11-26 1:08 ` Ingo Molnar
2004-11-26 0:34 ` Ingo Molnar
2004-11-26 0:37 ` Ingo Molnar
2004-11-26 8:52 ` Esben Nielsen
2004-11-26 16:26 ` Esben Nielsen
2004-11-26 20:41 ` Ingo Molnar
2004-11-26 21:05 ` Ingo Molnar
2004-11-27 23:05 ` Esben Nielsen
2004-11-28 8:42 ` Ingo Molnar
2004-11-28 15:55 ` Esben Nielsen
2004-11-29 9:59 ` Ingo Molnar
2004-11-29 15:07 ` Esben Nielsen
2004-11-29 15:56 ` Ingo Molnar
2004-11-29 15:57 ` Ingo Molnar
2004-11-29 16:50 ` Esben Nielsen
2004-11-30 8:49 ` Ingo Molnar
2004-11-22 9:23 ` Bill Huey
2004-11-22 12:37 ` Ingo Molnar
2004-11-22 21:25 ` Bill Huey
2004-11-22 14:16 ` john cooper
2004-11-22 15:24 ` Ingo Molnar
2004-11-23 1:19 ` john cooper
2004-11-23 8:13 ` Esben Nielsen
2004-11-23 9:21 ` Ingo Molnar
2004-11-22 21:30 ` Bill Huey
2004-11-23 1:34 ` john cooper [this message]
2004-11-22 16:12 ` Esben Nielsen
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=41A293B4.8000002@timesys.com \
--to=john.cooper@timesys.com \
--cc=bhuey@lnxw.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=simlo@phys.au.dk \
/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