mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Jason Low <jason.low2@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Waiman Long <Waiman.Long@hp.com>, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Scott J Norton <scott.norton@hp.com>,
	Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH v3] locking/rwsem: reduce spinlock contention in wakeup after up_read/up_write
Date: Tue, 28 Apr 2015 11:05:55 -0700	[thread overview]
Message-ID: <1430244355.2004.14.camel@stgolabs.net> (raw)
In-Reply-To: <1430243401.4463.4.camel@j-VirtualBox>

On Tue, 2015-04-28 at 10:50 -0700, Jason Low wrote:
> On Tue, 2015-04-28 at 19:17 +0200, Peter Zijlstra wrote:
> 
> > To me it makes more sense to reverse these two branches (identical code
> > wise of course) and put the special case first.
> > 
> > Alternatively we could also do something like the below, which to my
> > eyes looks a little better still, but I don't care too much.
> > 
> > 	if (rwsem_has_spinner(sem)) {
> > 		/*
> > 		 * comment ...
> > 		 */
> > 		 smp_rmb();
> > 		 if (!raw_spin_trylock_irqsave(&sem->wait_lock, flags))
> > 			return sem;
> > 		 goto locked;
> > 	}
> > 
> > 	raw_spin_lock_irqsave(&sem->wait_lock, flags);
> > locked:
> 
> How about putting this into its own function:

I'd actually prefer reusing the current function. We have so many
utility functions that we've over-encapsulated the code a bit, it makes
reading _harder_, imho.

Thanks,
Davidlohr


  parent reply	other threads:[~2015-04-28 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24 17:54 Waiman Long
2015-04-24 20:39 ` Davidlohr Bueso
2015-04-27 20:25   ` Waiman Long
2015-04-28 18:17     ` Davidlohr Bueso
2015-04-29 19:58       ` Waiman Long
2015-04-30 14:12         ` Davidlohr Bueso
2015-04-30 20:25           ` Waiman Long
2015-04-28 16:52 ` Peter Zijlstra
2015-04-28 17:17 ` Peter Zijlstra
2015-04-28 17:50   ` Jason Low
2015-04-28 17:59     ` Jason Low
2015-04-28 18:05     ` Davidlohr Bueso [this message]
2015-04-30 21:34   ` Waiman Long

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=1430244355.2004.14.camel@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=Waiman.Long@hp.com \
    --cc=doug.hatch@hp.com \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=scott.norton@hp.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

Powered by JetHome