Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: "Chris M. Thomasson" Newsgroups: comp.lang.c++ Subject: Re: signalling a condvar from inside vs. signalling a condvar von outside Date: Sat, 12 Apr 2025 12:33:57 -0700 Organization: A noiseless patient Spider Lines: 17 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 12 Apr 2025 21:33:58 +0200 (CEST) Injection-Info: dont-email.me; posting-host="982b471ae5e1b9b1e6a8cd05faa3439d"; logging-data="1262559"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19VeUaVOzNqO2bWPE4I9ahbHN29Afq8Pno=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:thb7E56kWTQSZA29U+v1TNdhADA= Content-Language: en-US In-Reply-To: Bytes: 1617 On 4/12/2025 8:23 AM, Bonita Montero wrote: [...] > It nearly doesn't matter in terms of numbers of context switches if > you  signal a condvar from inside our outside. The above program run > on a Zen4-CPU with WSL2: > >     inside: 20130 >     outside: 19811 > > On a 28 core Skylake-CPU with Ubuntu: > >     inside: 19997 >     outside: 19888 > There is a scalability problem wrt signalling inside the critical section. Does your convdar impl use wait morphing?