This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
LKML watch
- From: Masami Hiramatsu <hiramatu at sdl dot hitachi dot co dot jp>
- To: SystemTAP <systemtap at sources dot redhat dot com>
- Cc: Yumiko Sugita <sugita at sdl dot hitachi dot co dot jp>, Satoshi Oshima <soshima at redhat dot com>, Hideo Aoki <haoki at redhat dot com>
- Date: Thu, 02 Mar 2006 20:10:22 +0900
- Subject: LKML watch
Hi,
Here are issues posted on LKML in the last week.
OOM-killer too aggressive?
http://lkml.org/lkml/2006/2/26/58
We can track the memory allocation requests and find which request
actually kicks the OOM killer.
udevd is killing file write performance.
http://lkml.org/lkml/2006/2/22/80
The inotify locks a directory and udevd consumes a lot of cpu time.
http://lkml.org/lkml/2006/2/23/97
And in this mail, he traced back the stack to get the function arguments
by using kdb. I think we can provide some tracing scripts to do that.
NFS Still broken in 2.6.x?
http://lkml.org/lkml/2006/2/23/282
The performance of NFS server using linux2.6 is slower than linux2.4.
http://lkml.org/lkml/2006/2/24/151
And in this mail, he found the NFS performance degradation occurred
only with the "cfq" I/O scheduler. I think we can obtain how NFS
server works with I/O schedulers by using the systemtap.
Bio & Biovec-1 increasing cache size, never freed during disk IO
http://lkml.org/lkml/2006/2/25/184
This problem was solved. I think if we use the systemtap, we can find
the resource leaks by checking reference counter on enter and exit of
functions.
Re: lockd: couldn't create RPC handle for (host)
http://lkml.org/lkml/2006/2/27/302
NFS lockd has had a problem. It reported since Dec 18, 2005.
But the oops still occurs with 2.6.15.4. Some arguments or variables
may be corrupted. I think the systemtap can solve this problem
by tracing those variables.
--
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: hiramatu@sdl.hitachi.co.jp