Add nvcsw and nivcsw #772
Add nvcsw and nivcsw #772
Conversation
Add nvcsw and nivcsw -- number of voluntary context switches and number of involuntary context switches to platforms supporting these.
|
Sorry for the late reply. |
Add entries to README for NonvoluntaryContextSw (nivcsw, number of involuntary context switch) and VoluntaryContextSw (nvcsw, number of voluntary context switch).
| impl Column for NonVoluntaryContextSw { | ||
| fn add(&mut self, proc: &ProcessInfo) { | ||
| let (fmt_content, raw_content) = if let Some(ref status) = proc.curr_status { | ||
| if status.nonvoluntary_ctxt_switches.is_some() |
There was a problem hiding this comment.
Btw, involuntary is what everyone calls this. Not sure why this crate has it named differently. LMK if you would like this to be renamed involuntary.
There was a problem hiding this comment.
The name originates from the manual page of procfs.
https://man7.org/linux/man-pages/man5/proc_pid_status.5.html
voluntary_ctxt_switches
nonvoluntary_ctxt_switches
Number of voluntary and involuntary context switches
(since Linux 2.6.23).
nonvoluntary_ctxt_switches is the name of cat /proc/[PID]/status and "involuntary" is the description for users, so I think "involuntary" is appropriate for this context.
Rename NonVoluntaryContextSw to InvoluntaryContextSw. This is the more commonly used name for this metric.
|
Looks good! |
2 participants
Add nvcsw and nivcsw -- number of voluntary context switches and number of involuntary context switches to platforms supporting these. Roughly (and IIUC), voluntary context switches are when threads sleep or yield, involuntary are when threads are preempted.
I named these Voluntary and NonVoluntary context switches. I've seen both names used, not sure which is more common, but I think that is.
These are super useful for when working with performance and scheduler related things.