linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>,
	Clark Williams <williams@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH RT] rwsem_rt: Another (more sane) approach to mulit reader rt locks
Date: Tue, 22 May 2012 19:07:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1205221906250.3231@ionos> (raw)
In-Reply-To: <1337705539.13348.81.camel@gandalf.stny.rr.com>

On Tue, 22 May 2012, Steven Rostedt wrote:

> On Tue, 2012-05-22 at 18:40 +0200, Thomas Gleixner wrote:
> 
> > > I'm all for benchmarks. But right now, making all readers pass through a
> > > single mutex is a huge bottle neck for a lot of loads. Yes, they are
> > > mostly Java loads, but for some strange reason, our customers seems to
> > > like to run Java on our RT kernel :-p
> > 
> > I'm well aware that mmap_sem is a PITA but replacing one nightmare
> > with the next one is not the best approach.
> 
> Perhaps we could just change the mmap_sem to use this approach. Create a
> new type of rwsem/lock for -rt that we can be picky about.
> 
> Yeah, mmap_sem is a real PITA and it would be nice to have a solution
> that can be used until we can convert it to an RCU lock.

That still wants to be verified with numbers on a machine with at
least 32 cores and workloads which are mmap heavy. And before we don't
have such numbers we can really stop arguing about that solution.

Thanks,

	tglx

  reply	other threads:[~2012-05-22 17:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 14:03 [RFC][PATCH RT] rwsem_rt: Another (more sane) approach to mulit reader rt locks Steven Rostedt
2012-05-15 15:06 ` Peter Zijlstra
2012-05-15 15:42   ` Steven Rostedt
2012-05-15 17:25     ` Steven Rostedt
2012-05-15 17:31       ` Peter Zijlstra
2012-05-15 17:43         ` Steven Rostedt
2012-05-15 16:26 ` Steven Rostedt
2012-05-15 18:00 ` John Kacur
2012-05-15 18:14   ` Steven Rostedt
2012-05-17 15:18 ` Paul E. McKenney
2012-05-17 15:25   ` Paul E. McKenney
2012-05-17 15:32   ` Peter Zijlstra
2012-05-17 15:47     ` Paul E. McKenney
2012-05-17 16:17       ` Peter Zijlstra
2012-05-17 20:08         ` Paul E. McKenney
2012-05-17 20:20           ` Peter Zijlstra
2012-05-22 15:26 ` Thomas Gleixner
2012-05-22 15:50   ` Steven Rostedt
2012-05-22 16:40     ` Thomas Gleixner
2012-05-22 16:52       ` Steven Rostedt
2012-05-22 17:07         ` Thomas Gleixner [this message]
2012-05-22 17:50           ` 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=alpine.LFD.2.02.1205221906250.3231@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).