From: Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>
To: SystemTAP <systemtap@sources.redhat.com>
Cc: Yumiko Sugita <sugita@sdl.hitachi.co.jp>,
Satoshi Oshima <soshima@redhat.com>,
Hideo Aoki <haoki@redhat.com>
Subject: LKML watch
Date: Thu, 02 Mar 2006 11:10:00 -0000 [thread overview]
Message-ID: <4406D29E.5000606@sdl.hitachi.co.jp> (raw)
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
next reply other threads:[~2006-03-02 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 11:10 Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-30 15:29 LKML Watch Satoshi Oshima
2006-03-09 3:43 Hien Nguyen
2006-02-09 19:12 LKML watch Hien Nguyen
2006-02-03 23:59 Hien Nguyen
2006-02-02 17:00 LKML Watch Stone, Joshua I
2006-01-19 20:31 LKML watch Hien Nguyen
2006-01-26 16:58 ` William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4406D29E.5000606@sdl.hitachi.co.jp \
--to=hiramatu@sdl.hitachi.co.jp \
--cc=haoki@redhat.com \
--cc=soshima@redhat.com \
--cc=sugita@sdl.hitachi.co.jp \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).