From: "Peter W. Morreale" <pmorreale@novell.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: preempt-rt, need old style rwlocks for systemtap
Date: Sat, 03 May 2008 16:05:07 -0600 [thread overview]
Message-ID: <1209852307.5433.5.camel@hermosa.morrealenet> (raw)
In-Reply-To: <20080503171627.GC23961@redhat.com>
On Sat, 2008-05-03 at 13:16 -0400, Frank Ch. Eigler wrote:
> Hi -
>
> On Sat, May 03, 2008 at 09:34:16AM -0500, Clark Williams wrote:
> > [...]
> > > It has come to my attention that the preempt-rt patch suite
> > > deliberately defeats the potential concurrency intended by systemtap's
> > > use of rwlocks to permit concurrent readers [...]
>
> > The reason it "defeats" the concurrent behavior is that it's really
> > complicated to have concurrent readers with Priority Inheritance, so
> > the initial cut of rtmutexes serialized all lock accesses. [...]
>
> Do you believe priority inheritance to be an essential property of
> every use of these primitives, regardless of the nature of the
> specifical critical sections being protected? Is there no way & need
> to opt out of the extra machinery?
>
> - FChE
Yes, for (at least) two reasons. And No.
Without PI the best case is indeterminate latencies. The worst case is
deadlock. Please read Steven's excellent description of the issues in
the Documentation directory of a kernel tree.
Best,
-PWM
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-05-03 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 13:23 Frank Ch. Eigler
2008-05-03 14:34 ` Clark Williams
2008-05-03 17:16 ` Frank Ch. Eigler
2008-05-03 22:05 ` Peter W. Morreale [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=1209852307.5433.5.camel@hermosa.morrealenet \
--to=pmorreale@novell.com \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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
all inboxes | Powered by JetHome®