From: "Frank Ch. Eigler" <fche@redhat.com>
To: Clark Williams <williams@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: preempt-rt, need old style rwlocks for systemtap
Date: Sat, 3 May 2008 13:16:27 -0400 [thread overview]
Message-ID: <20080503171627.GC23961@redhat.com> (raw)
In-Reply-To: <481C77E8.8050002@redhat.com>
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
next prev parent reply other threads:[~2008-05-03 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 13:23 preempt-rt, need old style rwlocks for systemtap Frank Ch. Eigler
2008-05-03 14:34 ` Clark Williams
2008-05-03 17:16 ` Frank Ch. Eigler [this message]
2008-05-03 22:05 ` Peter W. Morreale
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=20080503171627.GC23961@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.