05-23-2012
Hi,
I have just posted almost the same question, not really that sure about how tha CPU I/O wait thing works in AIX - I'm told that it's not the same as Solaris which is what I normally work on.
So will be intereste to see what comes up in your thread as well as mine.
Regards
Dave
10 More Discussions You Might Find Interesting
1. AIX
Hello everyone
I have this process running on my server.
topas command
User 98.6 |############################
I have this process
Name PID CPU% PgSp Owner
db2fm 565264 25.6 1.5 ldapdb2
db2fm 348328 23.6 ... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
2. AIX
is there command which will display no of core per cpu in aix?
Regads,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
3. AIX
Hi.
I am looking for a command that will return me the amount of CPU used by a specific process in AIX environment.
I know there is TOPAS - but it is interactive and I need to get this information from system that connects remotely via SSH.
Using writing to files and than reading them is also... (1 Reply)
Discussion started by: yamsin789
1 Replies
4. Shell Programming and Scripting
Hi all,
I have a script that checks for the existence of files in a directory. Problem is,
if a file suddenly appears, I need to move it to another directory and then
call another program that does not import routines (within our DBMS).
Now, this script is ever running and uses the sleep... (3 Replies)
Discussion started by: gseyforth
3 Replies
5. Shell Programming and Scripting
Hi,
I need write a script that check how much CPU% a particular process is using so I execute something like :
while :
do
ps aux | awk '{ if($3 < 10) {printf( "this process %s CPU: %f and process %d\n",$1,$3,$2)}}'
sleep 300
done
but issue here is that I compare... (0 Replies)
Discussion started by: arizah
0 Replies
6. AIX
Hi
Could somebody explain me how AIX is using CPU??
For example when we have 2 processors system is giving all task to one of them till 100% is used ?? Or it's depend on configuration or anything else ??
Best regards
enda (3 Replies)
Discussion started by: enda
3 Replies
7. Shell Programming and Scripting
I want to write a shell script which will print AIX
CPU utilization
memory utilization
every 5 mins redirect to file. How do i do it? Please advise.
Which commands I should use? (3 Replies)
Discussion started by: vegasluxor
3 Replies
8. Shell Programming and Scripting
Hi,
I want to write one script that sent mail when CPU utilisation is more then 70%. i used topas but problem is it will show output only when we press ctrl +c.
Please let me know if there is some other command that will give cpu utilisation which i can use in shell script.
Thanks (3 Replies)
Discussion started by: ranvijaidba
3 Replies
9. SuSE
Hi Guys
I am running an Oracle database and most of my sessions are waiting for tcp.
Now, how do I check if tcp from the O/S level is servicing requests properly?
Please Help!!!
Thanks in advance... (4 Replies)
Discussion started by: Phuti
4 Replies
10. AIX
hi,
We have two LPARs, both have same capacity and believe same configuration. ulimit settings for oracle user is unlimited for both LPARs. Installed oracle databases with same configurations on both LPARs, both databases sync every second so volume is same. Both LPARs/databases have identical... (10 Replies)
Discussion started by: baladelaware73
10 Replies
LEARN ABOUT DEBIAN
cpu_throw
MI_SWITCH(9) BSD Kernel Developer's Manual MI_SWITCH(9)
NAME
mi_switch, cpu_switch, cpu_throw -- switch to another thread context
SYNOPSIS
#include <sys/param.h>
#include <sys/proc.h>
void
mi_switch(void);
void
cpu_switch(void);
void
cpu_throw(void);
DESCRIPTION
The mi_switch() function implements the machine independent prelude to a thread context switch. It is called from only a few distinguished
places in the kernel code as a result of the principle of non-preemptable kernel mode execution. The various major uses of mi_switch can be
enumerated as follows:
1. From within a function such as cv_wait(9), mtx_lock, or tsleep(9) when the current thread voluntarily relinquishes the CPU to wait
for some resource or lock to become available.
2. After handling a trap (e.g. a system call, device interrupt) when the kernel prepares a return to user-mode execution. This case
is typically handled by machine dependent trap-handling code after detection of a change in the signal disposition of the current
process, or when a higher priority thread might be available to run. The latter event is communicated by the machine independent
scheduling routines by calling the machine defined need_resched().
3. In the signal handling code (see issignal(9)) if a signal is delivered that causes a process to stop.
4. When a thread dies in thread_exit(9) and control of the processor can be passed to the next runnable thread.
5. In thread_suspend_check(9) where a thread needs to stop execution due to the suspension state of the process as a whole.
mi_switch() records the amount of time the current thread has been running in the process structures and checks this value against the CPU
time limits allocated to the process (see getrlimit(2)). Exceeding the soft limit results in a SIGXCPU signal to be posted to the process,
while exceeding the hard limit will cause a SIGKILL.
If the thread is still in the TDS_RUNNING state, mi_switch() will put it back onto the run queue, assuming that it will want to run again
soon. If it is in one of the other states and KSE threading is enabled, the associated KSE will be made available to any higher priority
threads from the same group, to allow them to be scheduled next.
After these administrative tasks are done, mi_switch() hands over control to the machine dependent routine cpu_switch(), which will perform
the actual thread context switch.
cpu_switch() first saves the context of the current thread. Next, it calls choosethread() to determine which thread to run next. Finally,
it reads in the saved context of the new thread and starts to execute the new thread.
cpu_throw() is similar to cpu_switch() except that it does not save the context of the old thread. This function is useful when the kernel
does not have an old thread context to save, such as when CPUs other than the boot CPU perform their first task switch, or when the kernel
does not care about the state of the old thread, such as in thread_exit() when the kernel terminates the current thread and switches into a
new thread.
To protect the runqueue(9), all of these functions must be called with the sched_lock mutex held.
SEE ALSO
cv_wait(9), issignal(9), mutex(9), runqueue(9), tsleep(9), wakeup(9)
BSD
November 24, 1996 BSD