From owner-freebsd-net Mon Feb 8 17:49:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11683 for freebsd-net-outgoing; Mon, 8 Feb 1999 17:49:49 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com ([209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11675 for ; Mon, 8 Feb 1999 17:49:47 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.1/8.9.1) with ESMTP id UAA58447 for ; Mon, 8 Feb 1999 20:49:42 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Mon, 8 Feb 1999 20:49:42 -0500 (EST) From: Jim Cassata To: FreeBSD Net Subject: bandwidth limiting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any decent bandwidth limiting software out there for FreeBSD? Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 8 18:22:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16547 for freebsd-net-outgoing; Mon, 8 Feb 1999 18:22:44 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA16533 for ; Mon, 8 Feb 1999 18:22:42 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 17394 invoked by uid 1001); 9 Feb 1999 02:22:46 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 08 Feb 1999 21:22:45 -0500 (EST) X-Face: *0^4Iw) To: Jim Cassata Subject: RE: bandwidth limiting Cc: FreeBSD Net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 09-Feb-99 Jim Cassata wrote: > > Is there any decent bandwidth limiting software out there for FreeBSD? man dummynet. It's built in. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 8 18:44:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19344 for freebsd-net-outgoing; Mon, 8 Feb 1999 18:44:07 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com ([209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19338 for ; Mon, 8 Feb 1999 18:44:05 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.1/8.9.1) with ESMTP id VAA58598; Mon, 8 Feb 1999 21:44:04 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Mon, 8 Feb 1999 21:44:04 -0500 (EST) From: Jim Cassata To: Vince Vielhaber cc: FreeBSD Net Subject: RE: bandwidth limiting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org is this only in 2.2.X? I don't see it on any 3.0 machines Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Mon, 8 Feb 1999, Vince Vielhaber wrote: > > On 09-Feb-99 Jim Cassata wrote: > > > > Is there any decent bandwidth limiting software out there for FreeBSD? > > man dummynet. It's built in. > > Vince. > -- > ========================================================================== > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > # include TEAM-OS2 > Online Campground Directory http://www.camping-usa.com > Online Giftshop Superstore http://www.cloudninegifts.com > ========================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 8 19:11:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22066 for freebsd-net-outgoing; Mon, 8 Feb 1999 19:11:24 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22061 for ; Mon, 8 Feb 1999 19:11:23 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA20842; Mon, 8 Feb 1999 19:08:57 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdB20840; Tue Feb 9 03:08:55 1999 Date: Mon, 8 Feb 1999 19:08:51 -0800 (PST) From: Julian Elischer To: Vince Vielhaber cc: Jim Cassata , FreeBSD Net Subject: RE: bandwidth limiting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org define "bandwidth limiting" there are many possible methods and answers. On Mon, 8 Feb 1999, Vince Vielhaber wrote: > > On 09-Feb-99 Jim Cassata wrote: > > > > Is there any decent bandwidth limiting software out there for FreeBSD? > > man dummynet. It's built in. > > Vince. > -- > ========================================================================== > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > # include TEAM-OS2 > Online Campground Directory http://www.camping-usa.com > Online Giftshop Superstore http://www.cloudninegifts.com > ========================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 8 19:13:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22797 for freebsd-net-outgoing; Mon, 8 Feb 1999 19:13:15 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com ([209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22792 for ; Mon, 8 Feb 1999 19:13:14 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.1/8.9.1) with ESMTP id WAA58662 for ; Mon, 8 Feb 1999 22:13:15 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Mon, 8 Feb 1999 22:13:14 -0500 (EST) From: Jim Cassata To: FreeBSD Net Subject: RE: bandwidth limiting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org defined as limiting colocation clients to X megabits over ethernet. Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Mon, 8 Feb 1999, Julian Elischer wrote: > define "bandwidth limiting" > there are many possible methods and answers. > > > On Mon, 8 Feb 1999, Vince Vielhaber wrote: > > > > > On 09-Feb-99 Jim Cassata wrote: > > > > > > Is there any decent bandwidth limiting software out there for FreeBSD? > > > > man dummynet. It's built in. > > > > Vince. > > -- > > ========================================================================== > > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > > # include TEAM-OS2 > > Online Campground Directory http://www.camping-usa.com > > Online Giftshop Superstore http://www.cloudninegifts.com > > ========================================================================== > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 9 04:19:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09672 for freebsd-net-outgoing; Tue, 9 Feb 1999 04:19:58 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09663 for ; Tue, 9 Feb 1999 04:19:55 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id NAA00924; Tue, 9 Feb 1999 13:19:49 +0100 (CET) (envelope-from des) To: Jim Cassata Cc: Vince Vielhaber , FreeBSD Net Subject: Re: bandwidth limiting References: From: Dag-Erling Smorgrav Date: 09 Feb 1999 13:19:48 +0100 In-Reply-To: Jim Cassata's message of "Mon, 8 Feb 1999 21:44:04 -0500 (EST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim Cassata writes: > On Mon, 8 Feb 1999, Vince Vielhaber wrote: > > On 09-Feb-99 Jim Cassata wrote: > > > Is there any decent bandwidth limiting software out there for FreeBSD? > > man dummynet. It's built in. > is this only in 2.2.X? I don't see it on any 3.0 machines It's been in 3.0 since 1998/12/21. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 9 06:51:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23953 for freebsd-net-outgoing; Tue, 9 Feb 1999 06:51:24 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23938 for ; Tue, 9 Feb 1999 06:51:21 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA128630806; Tue, 9 Feb 1999 04:00:06 -0500 Date: Tue, 9 Feb 1999 04:00:05 -0500 (EST) From: Bill Fumerola To: Jim Cassata Cc: FreeBSD Net Subject: Re: bandwidth limiting In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 8 Feb 1999, Jim Cassata wrote: > Is there any decent bandwidth limiting software out there for FreeBSD? A question answered both in the FAQ and in projects.html on the website. http://www.freebsd.org/FAQ/networking.html http://www.freebsd.org/projects/#networking - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 10 15:49:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10204 for freebsd-net-outgoing; Wed, 10 Feb 1999 15:49:23 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10196 for ; Wed, 10 Feb 1999 15:49:21 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 2A11B6 for ; Wed, 10 Feb 1999 17:49:20 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-net@FreeBSD.ORG Subject: Serious mbuf cluster leak.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Feb 1999 17:49:20 -0600 From: Chris Csanady Message-Id: <19990210234920.2A11B6@friley-185-205.res.iastate.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been seeing a nasty cluster leak in both 3.0 stable and 4.0 current as of today. Until now, I thougt maybe it was something in my driver, athough after much careful looking over my code, it simply does not look possible. Also, I downgraded to current of Dec 12, and the problem dissappears. The odd thing is that the clusters that leak don't seem to be attached to mbufs. Or at least there is not a 1-1 ratio. Following is netstat output after a while of running netpipe in streaming mode. (NPtcp -s; see ftp://ftp.scl.ameslab.gov/pub/netpipe) Also, the leak only becomes apparent when the send write size is very large--several hundred K to several megabytes. Does anyone have any idea what this may be? I really am not sure where to look aside from trying prorgressively newer kernels. Also, I only have alphas to test on right now.. puck:~> netstat -m 211/416 mbufs in use: 116 mbufs allocated to data 95 mbufs allocated to packet headers 1674/1688/2048 mbuf clusters in use (current/peak/max) 3480 Kbytes allocated to network (97% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 10 21:14:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21883 for freebsd-net-outgoing; Wed, 10 Feb 1999 21:14:38 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from thelab.hub.org (nat0716.mpoweredpc.net [142.177.190.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21865 for ; Wed, 10 Feb 1999 21:14:27 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id AAA06924 for ; Thu, 11 Feb 1999 00:05:20 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 11 Feb 1999 00:05:20 -0400 (AST) From: The Hermit Hacker To: freebsd-net@FreeBSD.ORG Subject: /usr/ports/net/queso ... inconsistent results and FBSD3.0-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi... Has anyone here tried the above port? Going from one FreeBSD 3.0S box to another 3.0S box, I'm lucky to get the same answer each time, and am wondering if this might be indicative of a bug...? atelier# ./queso -n 5 -t 10 -d hub.org Starting 131.162.138.103:12528 -> 209.47.145.100:80 IN #1 : 80->12529 S:0 A: 0 W:0000 U:0 F: RST IN #3 : 80->12531 S:0 A: 0 W:0000 U:0 F: RST IN #4 : 80->12532 S:1 A:+1 W:4000 U:0 F: ACK IN #6 : 80->12534 S:1 A:+1 W:4000 U:0 F: SYN ACK IN #0 : 80->12528 S:1 A:+1 W:4000 U:0 F: SYN ACK 209.47.145.100:80 * Specialix Jetstream 6000 Terminal Server (by wh@hillerzentri.de) Hub.Org is definitely not a Terminal Server of any kind...is this a problem with the program, our networking code...or just 'the Net' in general? Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 10 22:44:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01563 for freebsd-net-outgoing; Wed, 10 Feb 1999 22:44:30 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from thelab.hub.org (nat0716.mpoweredpc.net [142.177.190.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01558 for ; Wed, 10 Feb 1999 22:44:28 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id BAA07829 for ; Thu, 11 Feb 1999 01:37:24 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 11 Feb 1999 01:37:24 -0400 (AST) From: The Hermit Hacker To: freebsd-net@FreeBSD.ORG Subject: Re: /usr/ports/net/queso ... inconsistent results and FBSD3.0-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ignore...I went and go libpcap and queso compiled under Solaris also, same results...I'm going through the QueSO code right now and think I've found the "bug"...but it looks like a bug in his code, or the same bug in Solaris as in FreeBSD :) On Thu, 11 Feb 1999, The Hermit Hacker wrote: > > Hi... > > Has anyone here tried the above port? Going from one FreeBSD 3.0S > box to another 3.0S box, I'm lucky to get the same answer each time, and > am wondering if this might be indicative of a bug...? > > atelier# ./queso -n 5 -t 10 -d hub.org > Starting 131.162.138.103:12528 -> 209.47.145.100:80 > IN #1 : 80->12529 S:0 A: 0 W:0000 U:0 F: RST > IN #3 : 80->12531 S:0 A: 0 W:0000 U:0 F: RST > IN #4 : 80->12532 S:1 A:+1 W:4000 U:0 F: ACK > IN #6 : 80->12534 S:1 A:+1 W:4000 U:0 F: SYN ACK > IN #0 : 80->12528 S:1 A:+1 W:4000 U:0 F: SYN ACK > 209.47.145.100:80 * Specialix Jetstream 6000 Terminal Server (by wh@hillerzentri.de) > > Hub.Org is definitely not a Terminal Server of any kind...is this a problem > with the program, our networking code...or just 'the Net' in general? > > Thanks... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 11 01:43:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20447 for freebsd-net-outgoing; Thu, 11 Feb 1999 01:43:51 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20428; Thu, 11 Feb 1999 01:43:48 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 960A410; Thu, 11 Feb 1999 03:43:43 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: Serious mbuf cluster leak.. In-reply-to: Your message of "Wed, 10 Feb 1999 17:49:20 CST." <19990210234920.2A11B6@friley-185-205.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Feb 1999 03:43:43 -0600 From: Chris Csanady Message-Id: <19990211094343.960A410@friley-185-205.res.iastate.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After a while, I have determined the cause of the leak to be the following commit. Although, I can't seem to find any reason why it would cause this behavior--reverting these files fixes it. Any thoughts? fenner 1999/01/20 09:32:01 PST Modified files: sys/kern uipc_socket.c sys/netinet tcp_output.c tcp_usrreq.c tcp_var.h sys/sys protosw.h Log: Add a flag, passed to pru_send routines, PRUS_MORETOCOME. This flag means that there is more data to be put into the socket buffer. Use it in TCP to reduce the interaction between mbuf sizes and the Nagle algorithm. Based on: "Justin C. Walker" 's description of Apple's fix for this problem. Revision Changes Path 1.50 +4 -2 src/sys/kern/uipc_socket.c 1.32 +3 -2 src/sys/netinet/tcp_output.c 1.40 +7 -2 src/sys/netinet/tcp_usrreq.c 1.49 +18 -17 src/sys/netinet/tcp_var.h 1.26 +2 -1 src/sys/sys/protosw.h >I have been seeing a nasty cluster leak in both 3.0 stable and 4.0 >current as of today. Until now, I thougt maybe it was something in >my driver, athough after much careful looking over my code, it >simply does not look possible. Also, I downgraded to current of >Dec 12, and the problem dissappears. > >The odd thing is that the clusters that leak don't seem to be >attached to mbufs. Or at least there is not a 1-1 ratio. Following >is netstat output after a while of running netpipe in streaming >mode. (NPtcp -s; see ftp://ftp.scl.ameslab.gov/pub/netpipe) Also, >the leak only becomes apparent when the send write size is very >large--several hundred K to several megabytes. > >Does anyone have any idea what this may be? I really am not sure >where to look aside from trying prorgressively newer kernels. Also, >I only have alphas to test on right now.. > >puck:~> netstat -m >211/416 mbufs in use: > 116 mbufs allocated to data > 95 mbufs allocated to packet headers >1674/1688/2048 mbuf clusters in use (current/peak/max) >3480 Kbytes allocated to network (97% in use) >0 requests for memory denied >0 requests for memory delayed >0 calls to protocol drain routines > > >Chris Csanady > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 06:50:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20880 for freebsd-net-outgoing; Fri, 12 Feb 1999 06:50:16 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns1.elpn.com (ns1.elpn.com [209.194.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20762 for ; Fri, 12 Feb 1999 06:50:03 -0800 (PST) (envelope-from rosteen@elpn.com) Received: from elpn.com (cox.com [206.98.143.200]) by ns1.elpn.com (8.8.8/8.8.8) with ESMTP id EAA16379 for ; Fri, 12 Feb 1999 04:53:56 -0700 (MST) (envelope-from rosteen@elpn.com) Message-ID: <36C43F67.8DBD25A0@elpn.com> Date: Fri, 12 Feb 1999 09:49:11 -0500 From: rosteen Reply-To: rosteen@elpn.com X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: net@FreeBSD.ORG Subject: making an application run more processes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I would like to know if there is a way to run a program and have it take more than one process at a time. If I am dedicating a machine to do one job, I would like for it to be near 40 to 60 % loaded down with work running just this one program. I've done some searches in the archives without any results. If some can point me in the right direction, I would be deeply grateful. thanks, Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 11:59:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27328 for freebsd-net-outgoing; Fri, 12 Feb 1999 11:59:37 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27317; Fri, 12 Feb 1999 11:59:34 -0800 (PST) (envelope-from justin@rhapture.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id LAA50880; Fri, 12 Feb 1999 11:48:50 -0800 Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Fri, 12 Feb 1999 11:48:43 -0800 Received: from rhapture.apple.com (rhapture.apple.com [17.202.40.59]) by scv2.apple.com (8.8.5/8.8.5) with ESMTP id LAA12162; Fri, 12 Feb 1999 11:48:41 -0800 Received: (from justin@localhost) by walker3.apple.com (8.9.1/8.9.1) id JAA00622; Thu, 11 Feb 1999 09:15:30 -0800 (PST) Message-Id: <199902111715.JAA00622@walker3.apple.com> To: Chris Csanady Subject: Re: Serious mbuf cluster leak.. Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: "Your message of Wed, 10 Feb 1999 17:49:20 CST."<19990210234920.2A11B6@friley-185-205.res.iastate.edu> Date: Thu, 11 Feb 1999 09:15:29 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.104) MIME-Version: 1.0 (Apple Message framework v104) Content-Type: text/enriched; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org <= bold>7540,3813,2F35Hel= veticaOuch. I can say that our implementation doesn't seem to = suffer from this problem. Could be there's an issue in the use of = PRUS_* v. the socket state we use. The code in my kernel looks like: in sosend(): if (dontroute) so->so_options |=3D SO_DONTROUTE; if (resid > 0) so->so_state |=3D SS_MORETOCOME; s =3D splnet(); /* XXX = */ error =3D (*so->so_proto->pr_usrreq)(so, (flags & MSG_OOB) ? PRU_SENDOOB : PRU_SEND, top, addr, control); splx(s); if (dontroute) so->so_options &=3D ~SO_DONTROUTE; so->so_state &=3D ~SS_MORETOCOME; and in tcp_output(): if (len) { if (len =3D=3D tp->t_maxseg) goto send; if (!(so->so_state & SS_MORETOCOME)) { if ((idle || tp->t_flags & TF_NODELAY) && len + off >=3D so->so_snd.sb_cc) goto send; } if (tp->t_force) goto send; We've subjected this to countless (well, some, I'm sure, can count them = :-}) hours of thrashing for web server, file server, and other-server = types of uses, and haven't seen any (reports of) leakage like this. I'll look more closely at the results we see, to verify that we don't = have a problem. Regards, Justin From: = 7540,3813,2F35HelveticaChris Csanady = <0000,0000,0000 7540,3813,2F35Date: = 7540,3813,2F351999-02-11 01:51:17 = -08000000,0000,0000 7540,3813,2F35To: = 7540,3813,2F35freebsd-current@FreeBSD= .ORG0000,0000,0000 7540,3813,2F35Subject: = 7540,3813,2F35Re: Serious mbuf = cluster leak..0000,0000,0000 7540,3813,2F35Cc: = 7540,3813,2F35freebsd-net@FreeBSD.ORG= 0000,0000,0000 7540,3813,2F35In-reply-to: = 7540,3813,2F35"Your message of Wed, = 10 Feb 1999 17:49:20 = CST."<<19990210234920.2A11B6@friley-185-205.res.iastate.edu>= 0000,0000,0000 7540,3813,2F35X-Mailer: = 7540,3813,2F35exmh version 2.0.2 = 2/24/980000,0000,0000 7540,3813,2F35X-Loop: = 7540,3813,2F35FreeBSD.org0000,0000,0000 = OhlfsAfter a while, I have determined the cause of = the leak to be the0000,0000,0000 7540,3813,2F35following commit. Although, I can't = seem to find any reason why0000,0000,0000 7540,3813,2F35it would cause this = behavior--reverting these files fixes = it.0000,0000,0000 7540,3813,2F35Any = thoughts?0000,0000,0000 7540,3813,2F35fenner 1999/01/20 09:32:01 = PST0000,0000,0000 7540,3813,2F35 Modified = files:0000,0000,0000 7540,3813,2F35 sys/kern = uipc_socket.c 0000,0000,0000 7540,3813,2F35 sys/netinet = tcp_output.c tcp_usrreq.c tcp_var.h 0000,0000,0000 7540,3813,2F35 sys/sys protosw.h = 0000,0000,0000 7540,3813,2F35 = Log:0000,0000,0000 7540,3813,2F35 Add a flag, passed to pru_send = routines, PRUS_MORETOCOME. This0000,0000,0000 7540,3813,2F35 flag means that there is more data = to be put into the socket buffer.0000,0000,0000 7540,3813,2F35 Use it in TCP to reduce the = interaction between mbuf sizes and = the0000,0000,0000 7540,3813,2F35 Nagle = algorithm.0000,0000,0000 7540,3813,2F35 = 0000,0000,0000 7540,3813,2F35 Based on: "Justin C. Walker" = <'s description of = Apple's0000,0000,0000 7540,3813,2F35 fix for this = problem.0000,0000,0000 7540,3813,2F35 = 0000,0000,0000 7540,3813,2F35 Revision Changes = Path0000,0000,0000 7540,3813,2F35 1.50 +4 -2 = src/sys/kern/uipc_socket.c0000,0000,0000 7540,3813,2F35 1.32 +3 -2 = src/sys/netinet/tcp_output.c0000,0000,0000 7540,3813,2F35 1.40 +7 -2 = src/sys/netinet/tcp_usrreq.c0000,0000,0000 7540,3813,2F35 1.49 +18 -17 = src/sys/netinet/tcp_var.h0000,0000,0000 7540,3813,2F35 1.26 +2 -1 = src/sys/sys/protosw.h0000,0000,0000 7540,3813,2F35>I have been seeing a nasty cluster = leak in both 3.0 stable and 4.00000,0000,0000 7540,3813,2F35>current as of today. Until now, I = thougt maybe it was something in0000,0000,0000 7540,3813,2F35>my driver, athough after much = careful looking over my code, it0000,0000,0000 7540,3813,2F35>simply does not look possible. = Also, I downgraded to current of0000,0000,0000 7540,3813,2F35>Dec 12, and the problem = dissappears. 0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35>The odd thing is that the clusters = that leak don't seem to be0000,0000,0000 7540,3813,2F35>attached to mbufs. Or at least = there is not a 1-1 ratio. Following0000,0000,0000 7540,3813,2F35>is netstat output after a while of = running netpipe in streaming0000,0000,0000 7540,3813,2F35>mode. (NPtcp -s; see = ftp://ftp.scl.ameslab.gov/pub/netpipe) = Also,0000,0000,0000 7540,3813,2F35>the leak only becomes apparent when = the send write size is very0000,0000,0000 7540,3813,2F35>large--several hundred K to several = megabytes.0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35>Does anyone have any idea what this = may be? I really am not sure0000,0000,0000 7540,3813,2F35>where to look aside from trying = prorgressively newer kernels. Also,0000,0000,0000 7540,3813,2F35>I only have alphas to test on right = now..0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35>puck:~> netstat = -m0000,0000,0000 7540,3813,2F35>211/416 mbufs in = use:0000,0000,0000 7540,3813,2F35> 116 mbufs allocated to = data0000,0000,0000 7540,3813,2F35> 95 mbufs allocated to = packet headers0000,0000,0000 7540,3813,2F35>1674/1688/2048 mbuf clusters in use = (current/peak/max)0000,0000,0000 7540,3813,2F35>3480 Kbytes allocated to network = (97% in use)0000,0000,0000 7540,3813,2F35>0 requests for memory = denied0000,0000,0000 7540,3813,2F35>0 requests for memory = delayed0000,0000,0000 7540,3813,2F35>0 calls to protocol drain = routines0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35>Chris = Csanady0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35>To Unsubscribe: send mail to = majordomo@FreeBSD.org0000,0000,0000 7540,3813,2F35>with "unsubscribe freebsd-net" in = the body of the message0000,0000,0000 = 7540,3813,2F35>0000,0000,0000 7540,3813,2F35To Unsubscribe: send mail to = majordomo@FreeBSD.org0000,0000,0000 7540,3813,2F35with "unsubscribe freebsd-net" in = the body of the message0000,0000,0000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 12:53:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04961 for freebsd-net-outgoing; Fri, 12 Feb 1999 12:53:36 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04956; Fri, 12 Feb 1999 12:53:34 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA04612; Fri, 12 Feb 1999 12:53:19 -0800 (PST) Message-Id: <199902122053.MAA04612@lestat.nas.nasa.gov> To: justin@apple.com Cc: Chris Csanady , freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Serious mbuf cluster leak.. Reply-To: Jason Thorpe From: Jason Thorpe Date: Fri, 12 Feb 1999 12:53:18 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 11 Feb 1999 09:15:29 -0800 "Justin C. Walker" wrote: > I can say that our implementation doesn't seem to = > suffer from this problem. Could be there's an issue in the use of = > PRUS_* v. the socket state we use. The code in my kernel looks like: The NetBSD code looks pretty much just like this, and also does not suffer from an mbuf cluster leak of any kind. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 16:16:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29303 for freebsd-net-outgoing; Fri, 12 Feb 1999 16:16:17 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29285; Fri, 12 Feb 1999 16:16:15 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 93D2E10; Fri, 12 Feb 1999 18:16:13 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Thorpe Cc: justin@apple.com, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Serious mbuf cluster leak.. In-reply-to: Your message of "Fri, 12 Feb 1999 12:53:18 PST." <199902122053.MAA04612@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Feb 1999 18:16:13 -0600 From: Chris Csanady Message-Id: <19990213001613.93D2E10@friley-185-205.res.iastate.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Thu, 11 Feb 1999 09:15:29 -0800 > "Justin C. Walker" wrote: > > > I can say that our implementation doesn't seem to = > > suffer from this problem. Could be there's an issue in the use of = > > PRUS_* v. the socket state we use. The code in my kernel looks like: > >The NetBSD code looks pretty much just like this, and also does not >suffer from an mbuf cluster leak of any kind. I'll take a look at the NetBSD code when I have a chance. Are you sure you just have not seen it though? I only see it over gigabit ethernet, and even then only when doing lots of large writes. Perhaps it is a timing issue? I am only pointing out what I see. It does not happen with source from before this change--so what else should I think? You are welcome to take a glance at my driver, although I don't think it is the problem. There are only 2 places where clusters are touched, and they never become seperate from the mbuf header. But I don't see any mbuf leak.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 16:31:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01461 for freebsd-net-outgoing; Fri, 12 Feb 1999 16:31:48 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01438 for ; Fri, 12 Feb 1999 16:31:43 -0800 (PST) (envelope-from justin@scv2.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id QAA42768 for ; Fri, 12 Feb 1999 16:30:31 -0800 Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Fri, 12 Feb 1999 16:30:23 -0800 Received: from localhost (grinch.apple.com [17.202.43.163]) by scv2.apple.com (8.8.5/8.8.5) with ESMTP id QAA33646; Fri, 12 Feb 1999 16:30:21 -0800 Received: (from justin@localhost) by localhost (8.8.5/8.8.5) id QAA07269; Fri, 12 Feb 1999 16:20:03 -0800 Message-Id: <19990212162002.M5418@apple.com> Date: Fri, 12 Feb 1999 16:20:02 -0800 From: "Justin C. Walker" To: Chris Csanady , Jason Thorpe Cc: freebsd-net@FreeBSD.ORG Subject: Re: Serious mbuf cluster leak.. Reply-To: justin@apple.com References: <199902122053.MAA04612@lestat.nas.nasa.gov> <19990213001613.93D2E10@friley-185-205.res.iastate.edu> MIME-Version: 1.0 X-Mailer: Mutt 0.93.2i In-Reply-To: <19990213001613.93D2E10@friley-185-205.res.iastate.edu>; from Chris Csanady on Fri, Feb 12, 1999 at 06:16:13PM -0600 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 12, 1999 at 06:16:13PM -0600, Chris Csanady wrote: > > >On Thu, 11 Feb 1999 09:15:29 -0800 > > "Justin C. Walker" wrote: > > > > > I can say that our implementation doesn't seem to = > > > suffer from this problem. Could be there's an issue in the use of = > > > PRUS_* v. the socket state we use. The code in my kernel looks like: > > > >The NetBSD code looks pretty much just like this, and also does not > >suffer from an mbuf cluster leak of any kind. > > I'll take a look at the NetBSD code when I have a chance. Are you sure > you just have not seen it though? I only see it over gigabit ethernet, > and even then only when doing lots of large writes. Perhaps it is a > timing issue? > > I am only pointing out what I see. It does not happen with source from > before this change--so what else should I think? You are welcome to > take a glance at my driver, although I don't think it is the problem. > There are only 2 places where clusters are touched, and they never > become seperate from the mbuf header. But I don't see any mbuf leak.. Believe me, I understand. We've been beating on this code for months, with 10, 100, and Gigabit networking, using web server, high-volume UDP, file share, and other tests. That's no guarantee, of course, and different setups can manifest different behaviors and bugs. However, I do feel confident that we haven't seen leaks. Those would typically grind the system to a halt, or result in a noticeable downturn in performance, and we just don't see this (or, rather, we know the reasons for the problems we do see :-}). Could well be that there's a subtle difference in the two implementations that shows up this leak under stress. I haven't looked at the code, though, and can't really comment. Well, I could, but it wouldn't help :-} Regards, Justin BTW: I got mildly whacked by The Powers That Probably Are for exhuberance in the use of FreeBSD mailing lists, so I presume one of the lists should be dumped. I'm removing the -current list, but someone might forward if it's of interest. -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *---------------------------------------*------------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 12 18:10:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11432 for freebsd-net-outgoing; Fri, 12 Feb 1999 18:10:12 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11423 for ; Fri, 12 Feb 1999 18:10:08 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id SAA16268; Fri, 12 Feb 1999 18:10:05 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA18964; Fri, 12 Feb 1999 18:10:05 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id TAA24011; Fri, 12 Feb 1999 19:10:02 -0700 Message-ID: <36C4DEFA.6AE60366@softweyr.com> Date: Fri, 12 Feb 1999 19:10:02 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: rosteen@elpn.com CC: net@FreeBSD.ORG Subject: Re: making an application run more processes References: <36C43F67.8DBD25A0@elpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org rosteen wrote: > > Hello, > I would like to know if there is a way to run a program and have it take > more than one process at a time. If I am dedicating a machine to do one > job, I would like for it to be near 40 to 60 % loaded down with work > running just this one program. > I've done some searches in the archives without any results. If some can > point me in the right direction, I would be deeply grateful. There certainly isn't a utility that will do this, the application would have to be written to do so. Whether or not it would be any faster depends greatly on the application itself. If it is a compute-bound process, splitting it into multiple processes would slow it down due to the overhead of coordinating the processes, unless it performs a lot of parallel computations. Then, you'd still lose, unless your system has multiple CPUs. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message