From: "Frank Ch. Eigler" <fche@redhat.com>
To: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: preempt-rt, need old style rwlocks for systemtap
Date: Sat, 3 May 2008 09:23:27 -0400 [thread overview]
Message-ID: <20080503132327.GA28881@redhat.com> (raw)
Hi -
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 of various data
structures. Since systemtap's probe handlers are all atomic,
nonblocking, nonpreemptable, it does not seem like there is any
real-time-oriented benefit in this. What can we do to work around
this and permit reader concurrency again in preempt-rt?
- FChE
next reply other threads:[~2008-05-03 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 13:23 Frank Ch. Eigler [this message]
2008-05-03 14:34 ` preempt-rt, need old style rwlocks for systemtap Clark Williams
2008-05-03 17:16 ` Frank Ch. Eigler
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=20080503132327.GA28881@redhat.com \
--to=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/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