From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,3e3949298ed3b36
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: g2news1.google.com!postnews2.google.com!not-for-mail
From: wojtek@power.com.pl (Wojtek Narczynski)
Newsgroups: comp.lang.ada
Subject: Re: High CPU in tasking
Date: 26 Jun 2004 01:01:46 -0700
Organization: http://groups.google.com
Message-ID: <5ad0dd8a.0406260001.1d4917b6@posting.google.com>
References: <slrncdltli.nr.lutz@taranis.iks-jena.de>
NNTP-Posting-Host: 83.27.40.215
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1088236907 27416 127.0.0.1 (26 Jun 2004 08:01:47
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 26 Jun 2004 08:01:47 +0000 (UTC)
Xref: g2news1.google.com comp.lang.ada:1912
Date: 2004-06-26T01:01:46-07:00
List-Id: <comp.lang.ada>

Hello,

> Debugging turned out:
>   - Every writing to the ringbuffer wakes up all reader tasks.

This sounds like the "thundering herd" problem linux used to have with
acccept call. This has been fixed, so maybe in this case the problem
should be reported and eventually fixed, or is it required to wake em
all for some reason?

Regards,
Wojtek