mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de
Cc: Waiman.Long@hpe.com, jason.low2@hp.com, peter@hurleysoftware.com,
	dave@stgolabs.net, linux-kernel@vger.kernel.org
Subject: [PATCH -tip v2 0/2] locking/rwsem (xadd): Waiter enhacements.
Date: Fri, 13 May 2016 11:56:25 -0700	[thread overview]
Message-ID: <1463165787-25937-1-git-send-email-dave@stgolabs.net> (raw)

Changes from v1: https://lkml.org/lkml/2016/5/9/12
 - dropped READ_ONCE(sem->counter) patch -- we already have barriers
   (ie set_task_struct) in the loop, and therefore do not see stale
   variables.
 - Reworked and merged the other patches to get rid of the explicit
   waiter (reader) refcount. (peterz).

Hi,

This is a follow up series while reviewing Waiman's reader-owned
state work[1]. While I have based it on -tip instead of that change,
I can certainly rebase the series in some future iteration.
	
Changes are mainly around reader-waiter optimizations, in no particular
order. Has passed numerous DB benchmarks without things falling apart.
Full details are in each patch.

[1] http://permalink.gmane.org/gmane.linux.kernel/2216743

Thanks!

Davidlohr Bueso (2):
  locking/rwsem: Enable lockless waiter wakeup(s)
  locking/rwsem: Rework zeroing reader waiter->task

 kernel/locking/rwsem-xadd.c | 73 +++++++++++++++++++++++++++++----------------
 1 file changed, 48 insertions(+), 25 deletions(-)

-- 
2.8.1

             reply	other threads:[~2016-05-13 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 18:56 Davidlohr Bueso [this message]
2016-05-13 18:56 ` [PATCH 1/2] locking/rwsem: Enable lockless waiter wakeup(s) Davidlohr Bueso
2016-06-03 10:54   ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2016-05-13 18:56 ` [PATCH 2/2] locking/rwsem: Rework zeroing reader waiter->task Davidlohr Bueso
2016-06-03 10:55   ` [tip:locking/core] " tip-bot for Davidlohr Bueso

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=1463165787-25937-1-git-send-email-dave@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=Waiman.Long@hpe.com \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®