From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 21 Nov 2009 14:13:27 -0500
To: 9fans@9fans.net
Message-ID: <670f511bbb8adbd1a0dc5dbbc6b80676@ladd.quanstro.net>
In-Reply-To: <<20091121190132.GA14743@unknown>>
References: <<20091121190132.GA14743@unknown>>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] A trace of poolalloc in-kernel
Topicbox-Message-UUID: 9dee267e-ead5-11e9-9d60-3106f5b1d025

> I've gotten and graphed a quick trace of all requests in-kernel to poolalloc
> during a session with my terminal, where I booted up, created a few
> windows, built a kernel, and shutdown.
>
> http://grex.org/~vsrinivas/p9malloc-traces/
> (There's even some eye-candy!)
>
> Quick summary: 50% of all requests to poolalloc in kernel during this session
> were under 50 bytes. Sadness.
>
> Hopefully this is of some interest.

good work!  i believe you can use devtrace(3) to
accomplish the same thing as you did with gdb.

- erik