All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
	mingo@kernel.org, peterz@infradead.org,
	akpm@linux-foundation.org, jack@suse.cz,
	kirill.shutemov@linux.intel.com, mhocko@suse.com,
	mgorman@techsingularity.net, linux-kernel@vger.kernel.org,
	Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 1/5] locking: Introduce range reader/writer lock
Date: Wed, 29 Mar 2017 18:40:39 +0300	[thread overview]
Message-ID: <20170329154039.sbmk4hfrgstj4w3s@node.shutemov.name> (raw)
In-Reply-To: <20170329153133.GG27446@linux-80c1.suse>

On Wed, Mar 29, 2017 at 08:31:33AM -0700, Davidlohr Bueso wrote:
> On Wed, 29 Mar 2017, Laurent Dufour wrote:
> 
> > On 28/03/2017 18:58, Kirill A. Shutemov wrote:
> > > On Tue, Mar 28, 2017 at 09:39:18AM -0700, Davidlohr Bueso wrote:
> > > > I'll wait to see if there are any more concerns and send a v2 with your corrections.
> > > 
> > > Have you tried drop-in replacement of mmap_sem with full range lock?
> > > It would be interesting to see performance implication for this.
> > > 
> > 
> > I've a patch that replace the mmap_sem with a full range lock, it seems
> > to work fine for x86 and ppc64 for now. I'll send it soon.
> > But I didn't yet check for performance. What is the best way to that ?
> 
> I expect performance to take a measurable hit if we simply use full range
> lock as a drop in replacement. My rwsem vs range lock measurements were
> done with this in mind. We only win with range locks when improving the
> level of parallelism.

It would be hard sell if we would see performance degradation simple
single-threaded workload.

-- 
 Kirill A. Shutemov

  reply	other threads:[~2017-03-29 15:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  5:03 [PATCH 0/5] locking Introduce range reader/writer lock Davidlohr Bueso
2017-03-07  5:03 ` [PATCH 1/5] locking: " Davidlohr Bueso
2017-03-09 11:03   ` Jan Kara
2017-03-28 10:00   ` Laurent Dufour
2017-03-28 16:39     ` Davidlohr Bueso
2017-03-28 16:58       ` Kirill A. Shutemov
2017-03-29  8:38         ` Laurent Dufour
2017-03-29 15:31           ` Davidlohr Bueso
2017-03-29 15:40             ` Kirill A. Shutemov [this message]
2017-03-29 16:10               ` Davidlohr Bueso
2017-04-03 14:19       ` Laurent Dufour
2017-04-03 15:26         ` Davidlohr Bueso
2017-04-03 16:06           ` Jan Kara
2017-04-04 15:31             ` Davidlohr Bueso
2017-03-29  8:56   ` Peter Zijlstra
2017-03-29 15:12     ` Davidlohr Bueso
2017-03-29  8:59   ` Peter Zijlstra
2017-03-29  9:08   ` Peter Zijlstra
2017-03-29 15:05     ` Davidlohr Bueso
2017-03-29  9:11   ` Peter Zijlstra
2017-03-29  9:44   ` Peter Zijlstra
2017-03-29 10:35   ` Peter Zijlstra
2017-03-29 10:49   ` Peter Zijlstra
2017-03-29 15:14     ` Davidlohr Bueso
2017-03-30 14:56   ` Laurent Dufour
2017-03-30 17:13     ` Davidlohr Bueso
2017-03-07  5:03 ` [PATCH 2/5] locking/locktorture: Fix rwsem reader_delay Davidlohr Bueso
2017-03-07  5:03 ` [PATCH 3/5] locking/locktorture: Fix num reader/writer corner cases Davidlohr Bueso
2017-03-07  5:03 ` [PATCH 4/5] locking/locktorture: Support range rwlocks Davidlohr Bueso
2017-03-07  5:03 ` [PATCH 5/5] staging/lustre: Use generic range rwlock Davidlohr Bueso
2017-03-07  6:05   ` Oleg Drokin
2017-03-07  6:05     ` [lustre-devel] " Oleg Drokin
2017-03-08 15:02     ` Davidlohr Bueso
2017-03-09  8:56   ` kbuild test robot
2017-03-09  8:56     ` [lustre-devel] " kbuild test robot
2017-03-09 14:40   ` kbuild test robot
2017-03-09 14:40     ` [lustre-devel] " kbuild test robot

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=20170329154039.sbmk4hfrgstj4w3s@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=jack@suse.cz \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=ldufour@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 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.