From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!etsiig.uniovi.es!Tuya
From: Tuya@etsiig.uniovi.es (Javier Tuya Gonzalez)
Newsgroups: comp.lang.ada
Subject: Storage manager monitoring
Message-ID: <237*Tuya@etsiig.uniovi.es>
Date: 31 May 90 15:50:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

In article <24559@mimsy.umd.edu> , stuartw@mimsy.umd.edu writes:

>I'm developing a system that requires a lot of dynamic storage manipulation.
>For the first go, I'm keeping it simple by just using a generic package
>that keeps a list of freed objects and allocates from that list or uses
>NEW if the free list is empty (i.e. Booch's Storage_Manager_Sequential).

>Since I'm in the prototype stage, I'd like to keep some statistics on how
>big the free list gets, how many total allocations occured, etc.  My problem
>is how to report this information when the application exits.  

I have a suggestion:

You can create a separate task monitoring all actions of the storage manager 
package. This task waits for rendez-vous with storage manager and recieves
a message for each memory allocation/deallocation action. Also, this
task can retain theese statistics or flush them into a file.

In the definitive releaso of product y can easily eliminate all 
references to monitoring task.

Javier Tuya Gonzalez