From: Steven Rostedt <rostedt@goodmis.org>
To: Priyanka Gupta Jain <p.priyankagupta@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: looking for something like raw_rwlock_t or some optimization in rwlock_t in Linux 3.0
Date: Tue, 08 May 2012 11:17:24 -0400 [thread overview]
Message-ID: <1336490244.14207.185.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CACpc7petSnyR4qwE+F_b-OcdXc9+c5RRrX_u0TiLZnzy2eDWOg@mail.gmail.com>
On Mon, 2012-05-07 at 10:19 +0530, Priyanka Gupta Jain wrote:
> hi,
>
> I would really appreciate if someone can help in finding an
> alternative to rwlock_t.
> I want one particular rw_lock to behave as in native linux not as
> mutex of if there is any other optimization that I can do in that
> rwlock or in general to all rwlocks as well.
> This is required to boost the performance in case of multicore systems
>
Understood. We use to have a rwlock multi prio-inheritance logic. But it
ended up being too complex and prone to bugs. Prio-inheritance is
complex and adding multi users to this just makes it exponentially more.
If there's ways to get rid of rwlocks with rcu locks (which is not
always possible) then that would be the best solution.
Unfortunately, we don't have a current solution for this problem :-(
-- Steve
next prev parent reply other threads:[~2012-05-08 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 4:49 looking for something like raw_rwlock_t or some optimization in rwlock_t in Linux 3.0 Priyanka Gupta Jain
2012-05-08 15:17 ` Steven Rostedt [this message]
2012-05-16 1:36 ` Steven Rostedt
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=1336490244.14207.185.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=p.priyankagupta@gmail.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;
as well as URLs for NNTP newsgroup(s).