linux-kernel - Re: [PATCH v3] locking/rwsem: reduce spinlock contention in wakeup after up_read/up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1430243401.4463.4.camel@j-VirtualBox>
Date:	Tue, 28 Apr 2015 10:50:01 -0700
From:	Jason Low <jason.low2@...com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Waiman Long <Waiman.Long@...com>, Ingo Molnar <mingo@...nel.org>,
	linux-kernel@...r.kernel.org, Davidlohr Bueso <dave@...olabs.net>,
	Scott J Norton <scott.norton@...com>,
	Douglas Hatch <doug.hatch@...com>, jason.low2@...com
Subject: Re: [PATCH v3] locking/rwsem: reduce spinlock contention in wakeup
 after up_read/up_write

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:

static inline bool __rwsem_wake_acquire_wait_lock(sem)
{
	/*
	 *
	 * Comments
	 *
	 */
	if (unlikely(rwsem_has_spinner(sem))) {
		/*
		 * Comments
		 */
		smp_rmb();
		if (!raw_spin_trylock_irqsave(&sem->wait_lock, flags))
			return false;
	}

	return true;
}


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/