From owner-freebsd-hackers Mon Aug 14 0:37:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 13A2E37B696 for ; Mon, 14 Aug 2000 00:37:30 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7E7bRZ14244; Mon, 14 Aug 2000 00:37:27 -0700 (PDT) Date: Mon, 14 Aug 2000 00:37:27 -0700 From: Alfred Perlstein To: Jeff Rhyason Cc: hackers@FreeBSD.ORG Subject: Re: Collecting waiting statistics (simulation question) Message-ID: <20000814003727.K4854@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from rhyason@cpsc.ucalgary.ca on Mon, Aug 14, 2000 at 01:10:05AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeff Rhyason [000814 00:14] wrote: > Can anybody help me with a project I am working on? I am trying > to simulate different memory allocation policies for a discrete > event simulation course. Being the guy I am, I decided to > collect some real statistics from a real system. The difficulty > I've encountered is that I can't find how to make them accessible! > > Is there a way that I can log a large amount of statistics > regarding kernel memory allocator activity and make that > accessible to a user process? (Something like Solaris' > crash(1m) and kmalog) > > Thanks in advance for any comments! Using sysctls is probably the easiest way of doing it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message