From owner-freebsd-hackers Tue Jan 7 17:47:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA04089 for hackers-outgoing; Tue, 7 Jan 1997 17:47:10 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA04073 for ; Tue, 7 Jan 1997 17:47:02 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id RAA13373 for ; Tue, 7 Jan 1997 17:47:49 -0800 (PST) Received: (qmail 14403 invoked by uid 110); 8 Jan 1997 01:46:39 -0000 Message-ID: <19970108014639.14401.qmail@suburbia.net> Subject: Re: mmap() updates...how often? In-Reply-To: from The Hermit Hacker at "Jan 7, 97 08:45:50 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 8 Jan 1997 12:46:39 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > is done, it can go to the next frame. The problem with that is that the > server is currently able to write 20+frames/sec to the MMAP'd region...what > sort of slowdown can I expect if I have 1000 open sockets that each have to > have that control data written to, sequentially? Why not just put them all in the same process group, and send the process group a SIGUSR1 when new data is ready in the mmaped region? This will both inform the processes and wake them up at the same time. Further, if you make your handler just inc a volatile variable, then your main routine can work out how many frames its missed. Cheers, Julian.