src/lib/libmemstat/libmemstat.3, branch release/7.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2008-02-24T05:45:17+00:00

'RELENG_7_0_0_RELEASE'.

This commit was manufactured to restore the state of the 7.0-RELEASE image.

Tidy up markup and fix two bugs.

2005-11-21T17:18:34+00:00

The "Mbuf" zone was renamed "mbuf" to improve consistency, but the code

2005-08-15T10:24:20+00:00

example in libmemstat.3 was not updated to take this rename into account.
Update the example.

PR:		84946
Submitted by:	Wojciech A. Koszek 
MFC after:	1 day

Document kvm(3)-related error constants, and correct minor formatting

2005-08-09T22:19:30+00:00

nits.

Teach libmemstat(3) how to extract malloc(9) statistics using kvm(3),

2005-08-06T13:54:03+00:00

so that libmemstat can be used to view full memory statistics from
kernel core dumps and /dev/mem.  This is provided via a new query
function, memstat_kvm_malloc(), which is also automatically invoked
by memstat_kvm_all().  A kvm handle must be passed in.

This will allow malloc(9)-specific code to be removed from vmstat(8).

Add memstat_kvm_uma(), an implementation of a libmemstat(3) query routine

2005-08-01T19:07:39+00:00

that knows how to extract UMA(9) allocator statistics from a core dump or
live memory image using kvm(3).  The caller is expected to provide the
necessary kvm_t handle, which is then used by libmemstat(3).

With these changes, it is trivially straight forward to re-introduce
vmstat -z support on core dumps, which was lost when UMA was introduced.

In the short term, this requires including vm/ include files that are not
intended for extra-kernel use, requiring in turn some ugliness.

Having decided not to provide a libmemstat(3) error number to text

2005-07-24T01:41:47+00:00

conversion routine, now change my mind and add one, memstat_strerror(3),
which returns a const char * pointer to a string describing the error,
to be used on the results of memstat_mtl_geterror().

While here, also correct a minor typo in the HISTORY man page.

Pointers on improving ease of internationalization would be
appreciated.

MFC after:	1 day

Document additional aspects of libmemstat(3):

2005-07-24T01:29:30+00:00

- Short description of each memory type access method.

- Descriptions of libmemstat(3) errors and memstat_mtl_geterror(3).

MFC after:	1 day

UMA supports "secondary" zones, in which a second zone can be layered

2005-07-20T09:17:40+00:00

on top of a primary zone, sharing the same allocation "keg".  When
reporting statistics for zones, do not report the free items in the
keg as part of the free items in the zone, or those free items will
be reported more than once: for the primary zone, and then any
secondary zones off the primary zone.  Separately record and maintain
a kegfree statistic, and export via memstat_get_kegfree(), which is
available for use if needed.  Since items free'd back to the keg are
not fully initialized, and hence may not actually be available (since
secondary zone ctor-time initialization can fail), this makes some
amount of sense.

This change corrects a bug made visible in the libmemstat(3)
modifications to netstat: mbufs freed back to the keg from the
packet zone would be counted twice, resulting in negative values
being printed in the mbuf free count.

Some further refinement of reporting relating to secondary zones may
still be required.

Reported by:	ssouhlal
MFC after:	3 days

Provide more documentation on caller-owned storage in struct memory_type,

2005-07-15T11:28:21+00:00

as well as documenting MEMSTAT_MAXCALLER.

MFC after:	1 week