From owner-freebsd-hackers Tue Aug 29 8:47:26 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 180BB37B422 for ; Tue, 29 Aug 2000 08:47:23 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7TFlJj17313; Tue, 29 Aug 2000 08:47:19 -0700 (PDT) Date: Tue, 29 Aug 2000 08:47:19 -0700 From: Alfred Perlstein To: Jeff Rhyason Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Collecting waiting statistics (simulation question) Message-ID: <20000829084719.V18862@fw.wintelcom.net> References: <20191127095516.A42415@rhyason.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20191127095516.A42415@rhyason.com>; from jeff@rhyason.com on Wed, Nov 27, 2019 at 09:55:16AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeff Rhyason [000829 07:44] 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 a slew of sysctls would make it trivial, have a look at how sysctls are decared. You can then have a process that samples the sysctls from userland. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message