10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
2. AIX
Hi All,
I am trying to find out type of AIX servers , for eg : server A is eServer p5 520 , server B is pSeries 630-6C4 etc.
Can some one suggest me the best way to retrive this information through command line.
is there any direct command or script by which i can retrieve this information... (9 Replies)
Discussion started by: omkar.jadhav
9 Replies
3. AIX
Hi All,
I have some questions regarding the performance, MEMORY/ Virtual Memory (paging /swap space)
Please see the nmon-MEMORY stats from my AIX LPAR.
24 GB --> RAM
3456 MB --> Paging Space
│ Memory ───────────────────────────────────────────────────────────────────────
│... (8 Replies)
Discussion started by: System Admin 77
8 Replies
4. AIX
How to find the memory utilization of AIX server using svmon -G output.
Sample output for svmon -G command from my AIX test server,
size inuse free pin virtual
memory 4014080 3995443 18637 575916 1876393
pg space 1179648 ... (3 Replies)
Discussion started by: maruthu
3 Replies
5. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
6. AIX
Hi,
I would like to know how to find Total Memory of Vio Server? I have used command prtconf | grep Memory , though this command is showing allocated memory of vio server.
But I would like to find out Total Memory of VIO Server,
Though this can be find out using browser http://<ip address... (9 Replies)
Discussion started by: manoj.solaris
9 Replies
7. AIX
Hi,
please explain that how to find the rootcause of aix servers reboot itself.
Which log or commands should be used to analyse the reboot incident?
Please explain in detail. (3 Replies)
Discussion started by: cyberkingjk
3 Replies
8. AIX
Hi,
I would like to know how to find out frequency of memory, I have used the command prtconf but it is showing amt of ram available on server, it is not showing frequency.
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
9. UNIX for Advanced & Expert Users
Is there some way to tell what processes are attached to a shared memory segment? We have a system on which I perform "icps -ma" and there are several segments pending deletion having numerous processes attached to them and I can't tell what processes they are. Neither the creator's pid nor last... (7 Replies)
Discussion started by: DreamWarrior
7 Replies
10. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
CLOCKS(7) BSD Miscellaneous Information Manual CLOCKS(7)
NAME
clocks -- various system timers
SYNOPSIS
#include <time.h>
DESCRIPTION
HZ is not part of the application interface in BSD.
There are many different real and virtual (timekeeping) clocks with different frequencies:
o The scheduling clock. This is a real clock with frequency that happens to be 100. It is not available to applications.
o The statistics clock. This is a real clock with frequency that happens to be 128. It is not directly available to applications.
o The clock reported by clock(3). This is a virtual clock with a frequency that happens to be 128. Its actual frequency is given by the
macro CLOCKS_PER_SEC. Note that CLOCKS_PER_SEC may be floating point. Do not use clock(3) in new programs under FreeBSD. It is feeble
compared with getrusage(2). It is provided for ANSI conformance. It is implemented by calling getrusage(2) and throwing away informa-
tion and resolution.
o The clock reported by times(3). This is a virtual clock with a frequency that happens to be 128. Its actual frequency is given by the
macro CLK_TCK (deprecated; do not use) and by sysconf(_SC_CLK_TCK) and by sysctl(3). Note that its frequency may be different from
CLOCKS_PER_SEC. Do not use times(3) in new programs under FreeBSD. It is feeble compared with gettimeofday(2) together with
getrusage(2). It is provided for POSIX conformance. It is implemented by calling gettimeofday(2) and getrusage(2) and throwing away
information and resolution.
o The profiling clock. This is a real clock with frequency 1024. It is used mainly by moncontrol(3), kgmon(8) and gprof(1). Applications
should determine its actual frequency using sysctl(3) or by reading it from the header in the profiling data file.
o The mc146818a clock. This is a real clock with a nominal frequency of 32768. It is divided down to give the statistic clock and the
profiling clock. It is not available to applications.
o The microseconds clock. This is a virtual clock with frequency 1000000. It is used for most timekeeping in BSD and is exported to
applications in getrusage(2), gettimeofday(2), select(2), getitimer(2), etc. This is the clock that should normally be used by BSD
applications.
o The i8254 clock. This is a real clock/timer with a nominal frequency of 1193182. It has three independent time counters to be used. It
is divided down to give the scheduling clock. It is not available to applications.
o The TSC clock (64-bit register) on fifth-generation or later x86 systems. This is a real clock with a frequency that is equivalent to
the number of cycles per second of the CPU(s). Its frequency can be found using the machdep.tsc_freq sysctl, if it is available. It is
used to interpolate between values of the scheduling clock. It can be accessed using the PMIOTSTAMP request of perfmon(4).
o The ACPI clock. This is a real clock/timer with a nominal frequency of 3579545. It is accessed via a 24 or 32 bit register. Unlike the
TSC clock, it maintains a constant tick rate even when the CPU sleeps or its clock rate changes. It is not available to applications.
Summary: if HZ is not 1000000 then the application is probably using the wrong clock.
SEE ALSO
gprof(1), clock_gettime(2), getitimer(2), getrusage(2), gettimeofday(2), select(2), clock(3), moncontrol(3), times(3)
AUTHORS
This manual page was written by Jorg Wunsch after a description posted by Bruce Evans.
BSD
January 18, 2008 BSD