Originally posted by: johng99
This page makes me believe a program-file's memory segment will be considered computational:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.prftungd/doc/prftungd/real_memory_mngment.htm But when I try to examine segment attributes in AIX 5.3, I don't see such segments being tagged as computational. Am I looking at them the right way?
Here is one example. I use "svmon -P <pid>" to list the memory segments for "telnet", then use kdb to show some information about the program-file-segment, a shared-library text segment, and a data segment. Only the last two - both are working segments - are reported as "computational".
==> kdb
.........
(0)> scb 2 4401
VMM SCB Addr B078F05C Index 00000401 of 00000BD2 Segment ID: 00004401
PERSISTENT STORAGE SEGMENT - (BASE SEG)
> (_segtype)..... persistent segment
> (_bsid)........ large file primary segment
> (_required).... modlist required
segment info bits (_sibits) : 28000001
default storage prot key (_defkey) : 0
………….
(0)> scb 2 6c05b
VMM SCB Addr B077A0B4 Index 0000005B of 00000BD2 Segment ID: 0006C05B
WORKING STORAGE SEGMENT
> (_segtype)..... working segment
> (_defd)........ deferred disk alloc
> (_shrlib)...... shared library segment
> (_compseg)..... computational segment segment info bits (_sibits) : 48010000
default storage prot key (_defkey) : 1
default placement policy (_mpolicy) : 00 P_DEFAULT
……….
(0)> scb 2 60ab8
VMM SCB Addr B07B5A20 Index 00000AB8 of 00000BD2 Segment ID: 00060AB8
WORKING STORAGE SEGMENT
> (_segtype)..... working segment
> (_forkcow)..... fork copy-on-write
> (_defd)........ deferred disk alloc
> (_processdata). process specific data
> (_privseg)..... process private segment
> (_compseg)..... computational segment segment info bits (_sibits) : 88410000
default storage prot key (_defkey) : 2
default placement policy (_mpolicy) : 00 P_DEFAULT
segment's page size (_psx) : 00 ( 4K)
……….
John
#AIX-Forum