From owner-freebsd-current Sat Apr 25 01:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24607 for freebsd-current-outgoing; Sat, 25 Apr 1998 01:12:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24599 for ; Sat, 25 Apr 1998 01:12:52 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id EAA04399; Sat, 25 Apr 1998 04:12:35 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Tom cc: Eivind Eklund , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: sysctl from Linux (*envy*) In-reply-to: Your message of "Sat, 25 Apr 1998 00:52:13 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Apr 1998 04:12:35 -0400 Message-ID: <4395.893491955@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote in message ID : > I'm not aware of any program that does that. I'm not aware why any > application programmer would even think malloc'ing they aren't using is a > good idea. It just doesn't make sense on any modern VM system. Not all applications are programmed with a `modern VM system' in mind. E.g. up until relatively recently, INN hardly ever released memory, on the assumption that holding onto it was cheaper than releasing it. This doesn't help much when the VM system is a lot smarter than INN... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message