linux-kernel - Re: Why Semaphore Hardware-Dependent?

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: <17651.37281.67926.208085@cargo.ozlabs.ibm.com>
Date:	Tue, 29 Aug 2006 11:00:17 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	Andi Kleen <ak@...e.de>
Cc:	"Dong Feng" <middle.fengdong@...il.com>,
	"Christoph Lameter" <clameter@....com>,
	linux-kernel@...r.kernel.org
Subject: Re: Why Semaphore Hardware-Dependent?

Andi Kleen writes:

> > That's fair enough, but I would be opposed to 
> > making semaphores bigger 
> 
> If the code was out of lined bigger wouldn't make much difference

I was referring to the data size not the code size.

> That would leave the fast path, but does it help that much there
> to have a more complicated implementation?

The implementation of the fast path is basically atomic_inc/dec.
Nothing more complicated.

Paul.
-
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/