10-29-2008
Quote:
Originally Posted by
otheus
Thanks, radoulov, but I don't see a way for top to display "high system call rate" or "high I/O rates" anything like that.
[...]
Sorry for not being clear, I meant high CPU usage (due to the high system call rate).
You may try iostat -d -p to see I/O activity by partition and thus restrict the possibilities.
Quote:
Is there any way to see writes-per-second on a per process basis?
Well,
the first think that
I would begin with
starcing the top CPU consumers to see where the CPU cycles go.
Last edited by radoulov; 10-29-2008 at 05:22 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
I am working on a Solaris machine. When i use a particular software to generate some files, the log shows around 0 to 3 secs for generating each file. But the same when i see on the disk it shows double the time difference between two file generation.
For example if file A takes 0 secs... (7 Replies)
Discussion started by: nileshkarania
7 Replies
2. UNIX for Advanced & Expert Users
Dear All,
We are using AIX 5.2 with IBM pseries servers.
I want to check disk io for a running process.
Please if anybody can help me.
Thanks.
Aqeel Anwar (1 Reply)
Discussion started by: aqeelcu@hotmail
1 Replies
3. AIX
hi,
i am working on aix 5.2, i want to check disk i/o for any running process.
please if anybody can help me.
thanks
Aqeel Anwar (1 Reply)
Discussion started by: system-admin
1 Replies
4. Shell Programming and Scripting
Hello ,
Well I have some /tmp files which are growing very quickly..Can anyone suggest me a way to find which process is logging into this file :confused: ?
Thanks very much in Advance!!
Mohammed (2 Replies)
Discussion started by: Mohammed
2 Replies
5. UNIX for Dummies Questions & Answers
Hi
We are running an IBM P570 with AIX and Unidata.
The disk monitor in nmon is showing that one of our logical volumes is hitting 100% most of the time, and that 98% of it is write.
I am trying to identify the top processes in terms of disk IO, obviously particularly write so that we... (4 Replies)
Discussion started by: idwalton72
4 Replies
6. Linux
Hi,
The OS is SuSE Enterprise 11 and the system is HP WS460c G6 Blade with hardware disk array RAID 1 mirror. One disk was just replaced and the disk mirroring process is on its way. My question is how to follow up / monitor the disk mirroring process? I know hpacucli can do the job, but there... (0 Replies)
Discussion started by: aixlover
0 Replies
7. UNIX for Dummies Questions & Answers
I have multiple input files that I want to manipulate using a shell script. The files are called 250.1 through 250.1000 but I only want the script to manipulate 250.300 through 250.1000. Before I was using the following script to manipulate the text files:
for i in 250.*; do
|| awk... (4 Replies)
Discussion started by: evelibertine
4 Replies
8. Ubuntu
Hi,
I am using iostat and /proc/<pid>/status to determine the disk usage per process. I have a question regarding buffer cache. When I am reading a 10MB file, the counters I get show that <5MB of the file is read. Do the counters in iostat and /proc/<pid> reflect the amount of data that is... (2 Replies)
Discussion started by: fidelity
2 Replies
9. Emergency UNIX and Linux Support
In Our Production server I/O was very high, I Recived mail that Disk I/O was high, is it possible how to find which process Used this much I/O ?
Iam Using Ubuntu server 12.04.
Linux 3.9.3-x86_64-server33 (Li473-1200) 07/23/2014 _x86_64_ (8 CPU)
12:05:01 AM DEV ... (5 Replies)
Discussion started by: babinlonston
5 Replies
10. Open Source
Hello!
Need help to write a Linux script that can be run from windows using command/Cygwin/any other way. I am new to scripting, actually i am trying to automate server health check like free disk space, memory along with few services status, if any services is not running then start services ,... (7 Replies)
Discussion started by: Sayed Ibrahim
7 Replies
LEARN ABOUT NETBSD
xc_unicast
XCALL(9) BSD Kernel Developer's Manual XCALL(9)
NAME
xcall, xc_broadcast, xc_unicast, xc_wait -- cross-call interface
SYNOPSIS
#include <sys/xcall.h>
typedef void (*xcfunc_t)(void *, void *);
uint64_t
xc_broadcast(u_int flags, xcfunc_t func, void *arg1, void *arg2);
uint64_t
xc_unicast(u_int flags, xcfunc_t func, void *arg1, void *arg2, struct cpu_info *ci);
void
xc_wait(uint64_t where);
DESCRIPTION
The machine-independent xcall interface allows any CPU in the system to request that an arbitrary function be executed on any other CPU.
Sometimes it is necessary to modify hardware state that is tied directly to individual CPUs (such as a CPU's local timer), and these updates
can not be done remotely by another CPU. The LWP requesting the update may be unable to guarantee that it will be running on the CPU where
the update must occur, when the update occurs.
Additionally, it is sometimes necessary to modify per-CPU software state from a remote CPU. Where these update operations are so rare or the
access to the per-CPU data so frequent that the cost of using locking or atomic operations to provide coherency is prohibitive, another way
must be found.
Cross calls help to solve these types of problem. However, since this facility is heavyweight, it is expected that it will not be used
often.
xcall provides a mechanism for making ``low priority'' cross calls. The function to be executed runs on the remote CPU within a thread con-
text, and not from a software interrupt, so it can ensure that it is not interrupting other code running on the CPU, and so has exclusive
access to the CPU. Keep in mind that unless disabled, it may cause a kernel preemption.
xcall also provides a mechanism for making ``high priority'' cross calls. The function to be executed runs on the remote CPU within a
IPL_SOFTCLOCK software interrupt context, possibly interrupting other lower-priority code running on the CPU.
NOTES
Functions being called should be relatively lightweight. They may block on locks, but carefully and minimally, to not interfere with other
cross calls in the system.
FUNCTIONS
xc_broadcast(flags, func, arg1, arg2)
Call (*func)(arg1, arg2) on all CPUs in the system. Return a uint64_t ``ticket'' to xc_wait() on for the cross-call to complete.
flags should be XC_HIGHPRI for a "high priority" call, and 0 for a "low priority" call. xc_broadcast() should not be called from
interrupt context.
xc_unicast(flags, func, arg1, arg2, ci)
Like xc_broadcast(), but call (*func)() on only the CPU indicated by ci. xc_unicast() also returns a ``ticket''.
xc_wait(where)
Wait on the ``ticket'' returned by a prior xc_broadcast() or xc_unicast() for the corresponding cross-call to complete. xc_wait()
should be called from a thread context.
CODE REFERENCES
The xcall interface is implemented within the file sys/kern/subr_xcall.c.
SEE ALSO
kpreempt(9), percpu(9)
HISTORY
The xcall interface first appeared in NetBSD 5.0.
AUTHORS
Andrew Doran <ad@NetBSD.org>
BSD
October 24, 2011 BSD