pSOSystem System Calls - Read

pROBE+ and ESp System Calls log_event
table. How much pMONT affects the specification of kc_nmsgbuf depends on the
monitoring demands that you expect pMONT to meet.
The rate at which the system-wide buffer pool is replenished depends on the
communication medium used to communicate with the host. With a network, for
example, pMONT replenishes the buffer relatively quickly. You can estimate the
requirements for the application by considering the following ESp behaviors:
● A message is posted to a queue every time an object is created or deleted.
● A message is posted to a queue every time pMONT receives a request.
● A message is posted when data collection ends under any of the buffer management
options.
● Under the Transmit Buffer Management option, pMONT periodically sends
data to the host. Every time it does so, pMONT posts a message to a queue.
The rate at which this occurs depends on the data collection configuration
and the application.
● A message is posted to a queue at the end of every user-specified Perfmeter
update period.
● If the Stack Checking feature is on, a message is posted every time a stack
warning is generated.
If the trace buffer overflows because a large number of object creates or deletes
occur in a very short time, ERR_EV_FULL is generated, and pMONT disconnects
from the ESp tool. The way to prevent trace buffer overflow is to increase the buffer
size by increasing the kc_nlocobj entry in the pSOS+ configuration table.
However, this problem is not likely to occur in a time-critical environment.
pSOSystem System Calls 6-7
6