Kbase 13107: Netware Memory Pools Allocation and optimization
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Netware Memory Pools Allocation and optimization
Netware Memory Pool
Netware V3.x manages its RAM through the use of memory pools. These
memory pools are designed to be allocated and optimized based on how
they are used long term or short term. Rather than preallocating or
preassigning a lot of memory at installation time, most resources are
allocated on as needed basis. Netware has 6 memory pools:
FILE CACHE BUFFERS: Main memory pool:used for caching reads and writes
(not returnable after use)
CACHE NON-MOVABLE: Subpool used by Nlms, including Clib when loaded
causes fragmentation.
(returnable to file cache buffers)
CACHE MOVABLE: Subpool owned by Netware, used for internal system
tables that change size dynamically
-File allocation tables
-Directory entry tables
(not returnable to file cache buffers)
PERMANENT MEMORY: One-way allocation pool for long-term memory needs
Communication Buffers
Directory cache buffers
(not returnable to file cache buffers)
SEMI-PERMANENT: Subpool used by Lan and disk drivers
(returnable to permanent memory, but not to file cache buffers)
ALLOC SHORT TERM MEMORY: Pool used for small,short-term allocations:
-drive mapping
-user connection information
-queue manager tables
(not returnable to either permanent memory or to file
cache buffers; Allocated memory no longer being used
remains available in the subpool for other uses)
NOTE: PROGRESS DOES NOT MAKE DIRECT CALLS TO NETWARE'S MEMORY, WE ASK FOR MEMORY
THROUGH THE CLIB.NLM.
Progress Software Technical Support Note # 13107