Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

libmtmalloc(3lib) [opensolaris man page]

libmtmalloc(3LIB)						Interface Libraries						 libmtmalloc(3LIB)

NAME
libmtmalloc - multi-threaded memory allocator library SYNOPSIS
cc [ flag... ] file... -lmtmalloc [ library... ] #include <mtmalloc.h> DESCRIPTION
Functions in this library provide concurrent access to heap space. INTERFACES
The shared object libmtmalloc.so.1 provides the public interfaces defined below. See Intro(3) for additional information on shared object interfaces. free malloc mallocctl memalign realloc valloc FILES
/usr/lib/libmtmalloc.so.1 shared object /usr/lib/64/libmtmalloc.so.1 64-bit shared object ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsl (32-bit) | +-----------------------------+-----------------------------+ | |SUNWcslx (64-bit) | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
pvs(1), sbrk(2), Intro(3), malloc(3C), malloc(3MALLOC), mapmalloc(3MALLOC), mtmalloc(3MALLOC), attributes(5) SunOS 5.11 22 May 2003 libmtmalloc(3LIB)

Check Out this Related Man Page

libumem(3LIB)							Interface Libraries						     libumem(3LIB)

NAME
libumem - object-caching memory allocation library SYNOPSIS
cc [ flag... ] file... -lumem [ library... ] #include <umem.h> DESCRIPTION
Functions in this library provide fast, scalable object-caching memory allocation with multithreaded application support. In addition to the standard malloc(3C) family of functions and the more flexible umem_alloc(3MALLOC) family, libumem provides powerful object-caching ser- vices as described in umem_cache_create(3MALLOC). The libumem library also provides extensive debugging support, including detection of memory leaks, buffer overruns, multiple frees, use of uninitialized data, use of freed data, and many other common programming errors. See umem_debug(3MALLOC). INTERFACES
The shared object libumem.so.1 provides the public interfaces defined below. See Intro(3) for additional information on shared object interfaces. calloc free malloc memalign realloc umem_alloc umem_cache_alloc umem_cache_create umem_cache_destroy umem_cache_free umem_free umem_nofail_callback umem_zalloc valloc FILES
/usr/lib/libumem.so.1 shared object /usr/lib/64/libumem.so.1 64-bit shared object ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsl (32-bit) | +-----------------------------+-----------------------------+ | |SUNWcslx (64-bit) | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
Intro(3), malloc(3C), umem_alloc(3MALLOC), umem_cache_create(3MALLOC), umem_debug(3MALLOC), attributes(5) SunOS 5.11 22 May 2003 libumem(3LIB)
Man Page

2 More Discussions You Might Find Interesting

1. Solaris

Test program running taking much more time on high end server T5440 than low end server T5220

Hi all, I have written the following program and run on both T5440 and T5220 on same OS version. I found that T5540 server takes more time than T5220. Please find below the details. test1.cpp #include <iostream> #include <pthread.h> using namespace std; #define NUM_OF_THREADS 20... (17 Replies)
Discussion started by: sanjay_singh85
17 Replies

2. Red Hat

Free() corrupted unsorted chunks

We are migrating Pro*C code from SOLARIS to LINUX-Redhat. While migrating we face memory de-allocation issue intermittently when accessing large volume of data. Below is the part of the code(since code is big I am putting the part of the code where the issue comes): ... (8 Replies)
Discussion started by: Karunx
8 Replies