![]() | |||||||||||
Messages in this thread |
* Alexander Nyberg: >> Most other system resources can be tracked quite easily: disk space, >> CPU time, committed address space, even network I/O (with tcpdump and >> netstat -p). But there's no such thing for disk I/O.>> Why can't this be done be looking at the major faults a process causes? Because only paging results in major faults, normal I/O with read()/write() (or the p*() variants) does not. > One could quite easily hack up a tool to monitor I/O per process or > does it need to be very more precise? It would be nice to obtain file names, too. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2005-03-22 14:05 [from the cache] ©2003-2008 | |||||||||||