DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Using the crash(ADM) diagnostic tool

Examining use of STREAMS resources

You can use the strstat command of crash(ADM) to study how STREAMS resources are being used on the system. The output of this command is similar to that produced using the command netstat -m as described in the Performance Guide.

The following is an example of output from strstat:

> strstat
ITEM                  CONFIG    ALLOC    FREE         TOTAL     MAX    FAIL   BUFCALL
streams                  160       79      81          2515      89       0   -
queues                   452      374      78          5074     416       0   -
message headers          100       39      61        182337      87       0   -
buffer headers           314      194     120         46826     201       0   -
data block size   64      64        1      63        120940      49       0   -
data block size  128      32        0      32          1538       5       0   -
data block size  256      32        3      29          2995      19       0   -
data block size  512      16        8       8          5875      15       0   -
data block size   1Kb      8        0       8          2846       5       0   -
...
data block size 512Kb      0        0       0             0       0       0   -
  
Count of scheduled queues:   0
Number of unallocated pages: 466
Buffer splitting threshold: 80
Size of the interrupt pool: 20
Streams daemon (strd) flags:
The CONFIG column shows the total number of each resource that was configured for use, and MAX is the maximum number that have been allocated at any one time.

ALLOC is the number that are currently allocated, and TOTAL is the total number that have been used since the system was booted.

FAIL is the number of times that a resource was unavailable since the system was booted. Since data blocks are dynamically allocated from the memory reserved for use by STREAMS, you should not expect to see any value other than 0 in the this column.

See the Performance Guide for more information about examining and tuning STREAMS resources.


Next topic: Translating virtual addresses to physical addresses
Previous topic: Monitoring memory allocation

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005