From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13637 Path: news.gmane.org!.POSTED.ciao.gmane.org!not-for-mail From: Markus Wichmann Newsgroups: gmane.linux.lib.musl.general Subject: MSB in rwlock? Date: Tue, 22 Jan 2019 21:28:47 +0100 Message-ID: <20190122202847.GB23924@voyager> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.org; posting-host="ciao.gmane.org:195.159.176.228"; logging-data="196911"; mail-complaints-to="usenet@ciao.gmane.org" User-Agent: Mutt/1.10.1 (2018-07-13) To: musl@lists.openwall.com Original-X-From: musl-return-13653-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jan 22 21:29:48 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by ciao.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1gm2g3-000p2O-Sl for gllmg-musl@m.gmane.org; Tue, 22 Jan 2019 21:29:43 +0100 Original-Received: (qmail 3715 invoked by uid 550); 22 Jan 2019 20:29:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3676 invoked from network); 22 Jan 2019 20:29:40 -0000 Content-Disposition: inline X-Provags-ID: V03:K1:Q+QfiMXhZPOifs0pcwNRhlpRr5qRrlnLx2ND2BsRF5hWr/wOtfh DutEBpPa5Cv2Lhk2jfM6w0iRjm/TXSoCUo0jJprEbuQ7W5eA+Mki+AaxkFo7zJ6nU4q539S fKHV0Fvf3jisx6gXfnmQnUYgYiK1ql+Fo2fEJ2jVR3beVT6njB5IX/yy0fk3RYeBR4aP9YM 4ORTO3C9spd3G7wqiPCfQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:I4IOr/7FaMA=:C68azSh10wqp5M7HFMfo0n VheIQUzmVqIx9HemBIwhzaXaip7NYAussEYKz1iZsGauT+QaDg6yezs+A3mgK0iWCnUsy7w0S xU18feEmRVV7pa/PGPDTLTIcYhh1TU91+bm/UYrKBBKQcFIXrfSqNdtJIjWZbydZl9r8qLQzK Y1SzKlCOqB1Gv2ImdIopmCYBXSGjEGsFVW2HoUQTVHVK+C5R8vYJGoREzhiAV4KRX5rxsaI3R IRt1gMBbCvnu+Th7fuLnu8pbETrkXui6Unk8ahE6pBmd9kGBcAnNCxfYVDmcCpWPb3KyAAw5J OAstqtdJzpsI7afcc4bDEEPDy0fhADCb/yvZhG1U4oKhHR3f0oILgbAsiWhTjYjUqzMTbFFEI 95yQItkFgA8J93ViL9HwuzPisD0mUXGVOrMswXpW4tCuOc3Il8obRW8TzkMoh9u9zix1Va19V jGlPismDlbVMdsP4O/lDKCyQip+1Eq1kX9+SkAvFnjc0oG+/pDetOaAY3Tmi6R0JEVXbdA4bM sONJoBrK1z8AwDbQZ2zoO0Txr32BJZzEdhUqY2ReGpORJWdvtdxz5gXYFHchUnsxqbr0J+S1f fIZM5zi2xD20+WAiPfPjm+IXw7abTeIMLOBvo4WIhlkGxTd6936c6upyA3wSR6JiC5/1rfZBW TUqNyWYKqhcqQlZgQA43jYjESD90ytNbQKsEbF+TX+tGMr/3MmlhCM4NU/nbjrL5WVKfwFU9c hJxvWdFpaNrPsm5MAVAKvInDdT6jj94bILO7+araRVBkIClF8czjVhs+FPH2ifSeqOjdQiZh Xref: news.gmane.org gmane.linux.lib.musl.general:13637 Archived-At: Hi all, would someone kindly explain what the highest bit in the rwlock value is doing? As far as I can see, it is set whenever one of the locking functions enters a contended case, and cleared when the unlock function sets the lock to 0 (so when the last reader or the writer unlocks the rwlock). But at any other point the bit is masked out, AFAICS. So what is it doing? Or is it just a vestige that can be done away with? Ciao, Markus