From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
p.lundkvist@telia.com, linux-kernel@vger.kernel.org, rjw@sisk.pl,
Mark Lord <lkml@rtr.ca>
Subject: Re: [PATCH] Page writeback broken after resume: wb_timer lost
Date: Sat, 17 Jun 2006 09:12:51 +1000 [thread overview]
Message-ID: <200606170912.55334.ncunningham@linuxmail.org> (raw)
In-Reply-To: <20060616212410.GA6821@linuxtv.org>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hi.
Sorry for coming late to the party. I've only just seen this thread, and have
had reports of it too.
My concern is, shouldn't we be dealing with the cause rather than just one
symptom (and as Pavel rightly wondered, assuming there aren't more)? I'm not
sure that I have a solution, but I think the point is worth raising again.
Do we want something like adding the process's task struct to timer data, and
get the timer code to delay firing timers for frozen processes?
Regards,
Nigel
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-16 23:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 13:03 [PATCH] Page writeback broken after resume: wb_timer lost Peter Lundkvist
2006-05-20 17:37 ` Andrew Morton
2006-05-20 22:50 ` Pavel Machek
2006-05-21 0:12 ` Andrew Morton
2006-05-21 6:52 ` Peter Lundkvist
2006-05-21 10:08 ` Pavel Machek
2006-06-16 21:24 ` Johannes Stezenbach
2006-06-16 23:12 ` Nigel Cunningham [this message]
2006-06-19 15:41 ` Mark Lord
2006-06-21 3:38 ` Mark Lord
2006-06-21 3:54 ` Andrew Morton
2006-06-21 4:10 ` Mark Lord
2006-06-21 4:19 ` Andrew Morton
2006-06-22 20:25 ` Mark Lord
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=200606170912.55334.ncunningham@linuxmail.org \
--to=ncunningham@linuxmail.org \
--cc=akpm@osdl.org \
--cc=js@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=p.lundkvist@telia.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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