462190 page ins
6958561 page outs
...
856457822 zero filled pages faults
There is very little physical paging activity. What is happening a lot is the application is using memory for the first time and/or doing malloc.
Also, when physical i/o activity is taking place, you are writing 14x for each read
Code:
6958561/462190 (pages out / pages in)
Your high number is just showing what I hope is normal startup activity. You have lots of memory free - so file caching is easy (also explains why writes dominate read activity)
Last edited by MichaelFelt; 11-24-2012 at 12:35 PM..
Reason: correct layout of pasted data
Hello
Please can you tell me how to access COPY ON WRITE page faults in HP -UNIX.
I found the structure in
/usr/include/sys/vmmeter with the structure name vmmeter.
Please tell me the function to fill the values to this structure and also
the arguments for function.:: (5 Replies)
Hi,
Will anybody tell me what is this 'intransient blocking page faults' in HP-UX, it is in the structure _pst_vminfo in the header file /ust/include/sys/pstat/vm_pstat_body.h? (4 Replies)
Hi,
We are running SUN sparc 5.8, notice frequent "Page Faults" message from our monitor s/w "ServerVantage" coming but no message display in SUN syslog or messages log. Any ideas why or what to check?
thanks,
Ahmad (2 Replies)
Hi,
Currently I'm experience very high page ins on my system running on solaris 10.
From vmstat, the page ins figure is very high, further drill down shows the page ins are from file system and occassional spike in executable page ins.
Details as follow:
oracle@perch:/files>> vmstat 5... (9 Replies)
Hello,
I've been reading your forums for quite a while and the great amount of information I find here always come in hand.This time however, I need some specific help...
I have a doubt with an AIX server which I'm failing to understand as I'm new to its concept of memory management...
... (8 Replies)
Hi,
OS = AIX 5.3
Large number of page faults recently start to occure on AIX 5.3 lpar with mysql database installed. I need help in setting AIX OS parameter to solve the paging problem and some guidance on interpreting my stats
t
Code:
# vmstat... (5 Replies)
Hi,
Can someone help and give the answer for the following questions:
1. When PowerHA SystemMirror 7.1 is installed on AIX 7.1, what RSCT component does Cluster Aware AIX (CAA) replace?
A. Group Services
B. Resource Manager
C. Topology Services
D. Resource Monitoring and Control... (2 Replies)
Hi guys,
I have a zone on a M5000 server running solaris 10. The zone has an SAP application running on it and facing some performance issues. As part of the troubleshooting, I've been recommended to look for any paging on the OS. Please advise how to look for the paging.
I've been looking at... (4 Replies)
I am new to AIX but not new to unix.
I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs
From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
Discussion started by: mathisecure
2 Replies
LEARN ABOUT OPENSOLARIS
ddi_check_acc_handle
ddi_check_acc_handle(9F) Kernel Functions for Drivers ddi_check_acc_handle(9F)NAME
ddi_check_acc_handle, ddi_check_dma_handle - Check data access and DMA handles
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_check_acc_handle(ddi_acc_handle_t acc_handle );
int ddi_check_dma_handle(ddi_dma_handle_t dma_handle );
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
PARAMETERS
acc_handle Data access handle obtained from a previous call to ddi_regs_map_setup(9F), ddi_dma_mem_alloc(9F), or similar function.
dma_handle DMA handle obtained from a previous call to ddi_dma_setup(9F) or one of its derivatives.
DESCRIPTION
The ddi_check_acc_handle() and ddi_check_dma_handle() functions check for faults that can interfere with communication between a driver and
the device it controls. Each function checks a single handle of a specific type and returns a status value indicating whether faults
affecting the resource mapped by the supplied handle have been detected.
If a fault is indicated when checking a data access handle, this implies that the driver is no longer able to access the mapped registers
or memory using programmed I/O through that handle. Typically, this might occur after the device has failed to respond to an I/O access
(for example, has incurred a bus error or timed out). The effect of programmed I/O accesses made after this happens is undefined; for exam-
ple, read accesses (for example, ddi_get8(9F)) may return random values, and write accesses (for example, ddi_put8(9F)) may or may not have
any effect. This type of fault is normally fatal to the operation of the device, and the driver should report it via
ddi_dev_report_fault(9F) specifying DDI_SERVICE_LOST for the impact, and DDI_DATAPATH_FAULT for the location.
If a fault is indicated when checking a DMA handle, it implies that a fault has been detected that has (or will) affect DMA transactions
between the device and the memory currently bound to the handle (or most recently bound, if the handle is currently unbound). Possible
causes include the failure of a component in the DMA data path, or an attempt by the device to make an invalid DMA access. The driver may
be able to continue by falling back to a non-DMA mode of operation, but in general, DMA faults are non-recoverable. The contents of the
memory currently (or previously) bound to the handle should be regarded as indeterminate. The fault indication associated with the current
transaction is lost once the handle is (re-)bound, but because the fault may persist, future DMA operations may not succeed.
Note that some implementations cannot detect all types of failure. If a fault is not indicated, this does not constitute a guarantee that
communication is possible. However, if a check fails, this is a positive indication that a problem does exist with respect to communication
using that handle.
RETURN VALUES
The ddi_check_acc_handle() and ddi_check_dma_handle() functions return DDI_SUCCESS if no faults affecting the supplied handle are detected
and DDI_FAILURE if any fault affecting the supplied handle is detected.
EXAMPLES
static int
xxattach(dev_info_t *dip, ddi_attach_cmd_t cmd)
{
...
/* This driver uses only a single register-access handle */
status = ddi_regs_map_setup(dip, REGSET_ZERO, ®addr,
0, 0, , &acc_attrs, &acc_hdl);
if (status != DDI_SUCCESS)
return (DDI_FAILURE);
...
}
static int
xxread(dev_t dev, struct uio *uio_p, cred_t *cred_p)
{
...
if (ddi_check_acc_handle(acc_hdl) != DDI_SUCCESS) {
ddi_dev_report_fault(dip, DDI_SERVICE_LOST,
DDI_DATAPATH_FAULT, "register access fault during read");
return (EIO);
}
...
CONTEXT
The ddi_check_acc_handle() and ddi_check_dma_handle() functions may be called from user, kernel, or interrupt context.
SEE ALSO ddi_regs_map_setup(9F), ddi_dma_setup(9F), ddi_dev_report_fault(9F), ddi_get8(9F), ddi_put8(9F)SunOS 5.11 13 August 1999 ddi_check_acc_handle(9F)