linux-kernel - Re: [PATCH 2.6.20-rc4 3/4] futex_requeue

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: <45A4A102.6050006@bull.net>
Date:	Wed, 10 Jan 2007 09:17:06 +0100
From:	Pierre Peiffer <pierre.peiffer@...l.net>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Dinakar Guniguntala <dino@...ibm.com>,
	Jean-Pierre Dion <jean-pierre.dion@...l.net>,
	Jakub Jelinek <jakub@...hat.com>,
	Darren Hart <dvhltc@...ibm.com>,
	Sébastien Dugué <sebastien.dugue@...l.net>
Subject: Re: [PATCH 2.6.20-rc4 3/4] futex_requeue_pi optimization

Ulrich Drepper wrote :
> 
> So, this patch implements requeuing from a non-PI futex to a PI futex?

Yes.

> That's the bare minimum needed.  What about PI to PI?

I may miss something, but I don't think there is a need for that.

Currently, futex_requeue is (only) used in pthread_cond_broadcast to requeue 
some threads from an internal futex (futex1) to another futex (futex2, which is 
the futex behind the cond_mutex)

futex1 does not need to be a PI-futex, I think.

-- 
Pierre
-
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/