[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1400077624.9356.6.camel@buesod1.americas.hpqcorp.net>
Date: Wed, 14 May 2014 07:27:04 -0700
From: Davidlohr Bueso <davidlohr@...com>
To: mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, peterz@...radead.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
Cc: 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 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.
--
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/
Powered by blists - more mailing lists