From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12401 invoked by uid 1002); 22 Jul 2003 17:07:47 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 23961 invoked from network); 22 Jul 2003 17:07:47 -0000 From: "Jeff Adams" To: Date: Tue, 22 Jul 2003 10:07:41 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: [gentoo-dev] What is the fastest mechanism for ipc communication under the gentoo-sources kernel X-Archives-Salt: 03181145-b2d5-4936-957f-09561ceb8210 X-Archives-Hash: c84e242eef3f688c72412918bee50c07 Hello, I have a producer process that makes updates to shared memory. I need to notify consumer processes (potentially multiple) as quickly as possible. What I am looking for is a fast "wake-up" mechanism and a synchronization mechanism so that events are not lost. I'm currently using semaphores as the wake up mechanism. Question is this the fastest way to do this without going into a tight loop (waste of processor cycles)? I'd also have the issue of clients showing up asynchronously. If I just use semaphores counts based on the number of clients I run the risk of missing a client. Also if the clients process events too slowly then the producer will keep incrementing the semaphore beyond the client count. Then if one client is faster than the others it may get awakened multiple times for the same event. Any suggestions? Thanks in advance! -- gentoo-dev@gentoo.org mailing list