Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!raubtier-asyl.eternal-september.org!.POSTED!not-for-mail From: Bonita Montero Newsgroups: comp.lang.c++ Subject: Re: signalling a condvar from inside vs. signalling a condvar von outside Date: Wed, 16 Apr 2025 06:12:20 +0200 Organization: A noiseless patient Spider Lines: 11 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 16 Apr 2025 06:11:48 +0200 (CEST) Injection-Info: raubtier-asyl.eternal-september.org; posting-host="4aba3e0e947712b3737eebdc0f3c8caf"; logging-data="1448439"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19VxLIeHZQDRubwLQZIXERoybM+pSPArfM=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:9gEw1Z40fA+H7l1Y0kRMfgvzpX0= Content-Language: de-DE In-Reply-To: Bytes: 1857 Am 15.04.2025 um 21:07 schrieb Chris M. Thomasson: > In real applications there is generally more going on in those critical > sections vs your test... Well, I have seen some horror shows in my life. > > Again, think of a scenario where the lock is held. The thread signals... > Another thread wakes up and has to instantly block on a wait morphing > queue in the kernel. Not with glibc.