linux-kernel - Re: [tip:locking/core] rwsem: Add comments to explain the meaning of the rwsem's count field

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] [day] [month] [year] [list]

Date:	Wed, 14 May 2014 16:53:45 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Davidlohr Bueso <davidlohr@...com>
Cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, tim.c.chen@...ux.intel.com,
	peter@...leysoftware.com, jason.low2@...com, riel@...hat.com,
	alex.shi@...aro.org, paulmck@...ux.vnet.ibm.com,
	akpm@...ux-foundation.org, tglx@...utronix.de, walken@...gle.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:locking/core] rwsem: Add comments to explain the meaning of
 the rwsem's count field

On Wed, May 14, 2014 at 07:27:04AM -0700, Davidlohr Bueso wrote:
> On Mon, 2014-05-05 at 01:46 -0700, tip-bot for Tim Chen wrote:
> > Commit-ID:  3cf2f34e1a3d4d5ff209d087925cf950e52f4805
> > Gitweb:     http://git.kernel.org/tip/3cf2f34e1a3d4d5ff209d087925cf950e52f4805
> > Author:     Tim Chen <tim.c.chen@...ux.intel.com>
> > AuthorDate: Fri, 2 May 2014 12:53:57 -0700
> > Committer:  Ingo Molnar <mingo@...nel.org>
> > CommitDate: Sun, 4 May 2014 20:34:26 +0200
> > 
> > rwsem: Add comments to explain the meaning of the rwsem's count field
> > 
> > It took me quite a while to understand how rwsem's count field
> > mainifested itself in different scenarios.
> > 
> > Add comments to provide a quick reference to the the rwsem's count
> > field for each scenario where readers and writers are contending
> > for the lock.
> > 
> > Hopefully it will be useful for future maintenance of the code and
> > for people to get up to speed on how the logic in the code works.
> 
> sigh, after this commit, the opt spin patch no longer applies, I'm
> rebasing and send out v5.

No worries, fixed it already.

Content of type "application/pgp-signature" skipped