From: Mike Galbraith <efault@gmx.de>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.1 & D state processes
Date: Thu, 20 Apr 2006 08:51:19 +0200 [thread overview]
Message-ID: <1145515879.9712.11.camel@homer> (raw)
In-Reply-To: <1145515521.9712.8.camel@homer>
On Thu, 2006-04-20 at 08:45 +0200, Mike Galbraith wrote:
> Good idea. What time source are you using? I'd try plain old pit.
(Looking back, I see you're using pm timer.)
next prev parent reply other threads:[~2006-04-20 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 23:49 2.6.16.1 & D state processes Srihari Vijayaraghavan
2006-04-18 4:03 ` Andrew Morton
2006-04-18 5:07 ` Srihari Vijayaraghavan
2006-04-18 6:30 ` Mike Galbraith
2006-04-18 9:35 ` Srihari Vijayaraghavan
2006-04-18 12:47 ` Mike Galbraith
2006-04-20 5:54 ` Srihari Vijayaraghavan
2006-04-20 6:45 ` Mike Galbraith
2006-04-20 6:51 ` Mike Galbraith [this message]
2006-05-03 7:04 ` Srihari Vijayaraghavan
2006-05-03 7:18 ` Mike Galbraith
2006-05-08 0:57 ` Srihari Vijayaraghavan
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=1145515879.9712.11.camel@homer \
--to=efault@gmx.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sriharivijayaraghavan@yahoo.com.au \
/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