On Fri, 23 Sep 2005, Shanker Balan wrote:
See top(1):
m Toggle the display between 'cpu' and 'io' modes.
Thanks for the feedback.
had not had a chace to read lists for weeks..
That does exactly what I need.
My only complain is that once one switches to that mode that the default
sor
Thomas Hurst wrote:
* martinko ([EMAIL PROTECTED]) wrote:
well, thanks for the switch. i couldn't find any
description/explanation of/on the columns (VCSW,..) in top(1) man
page, though. :(
VCSW = Voluntary Context Switch
IVCSW = Involuntary Context Switch
A very nice article on the meanin
* martinko ([EMAIL PROTECTED]) wrote:
> well, thanks for the switch. i couldn't find any
> description/explanation of/on the columns (VCSW,..) in top(1) man
> page, though. :(
VCSW = Voluntary Context Switch
IVCSW = Involuntary Context Switch
A very nice article on the meaning of these is here:
Shanker Balan wrote:
Hello,
Francisco Reyes wrote,
On Fri, 23 Sep 2005, Joseph Koshy wrote:
Is there a way to find out which program(s) are causing the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
Looking at the man page it's non-obvious how to use it (to me).
Sp
Francisco Reyes wrote:
On Fri, 23 Sep 2005, Joseph Koshy wrote:
Is there a way to find out which program(s) are causing
the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
Looking at the man page it's non-obvious how to use it (to me).
Specially it seems one needs to
Hello,
Francisco Reyes wrote,
> On Fri, 23 Sep 2005, Joseph Koshy wrote:
>
> >>Is there a way to find out which program(s) are causing the I/O?
> >
> >ktrace(8); you can use it to trace all descendants of 'init'.
>
> Looking at the man page it's non-obvious how to use it (to me).
>
>
> Special
On Fri, 23 Sep 2005, Joseph Koshy wrote:
Is there a way to find out which program(s) are causing
the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
Looking at the man page it's non-obvious how to use it (to me).
Specially it seems one needs to indicate a pid or a comman
> Is there a way to find out which program(s) are causing
> the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-performance@freebsd.org mailing list
http://lists.
Looking at vmstat I see the "b" colun never hits zero and it's usually
between 5 and 20.
Is there a way to find out which program(s) are causing the I/O?
In some of the machines it was near trivial to find the culprit, but have
a handfull of machines that I am not sure what the cause of I/O is
