Re: Hibernation Redesign
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
- Date: Wed, 11 Jul 2007 14:09:39 +0200
Freezing of tasks is slowing down suspend. Don't know how serious
this is, suspend is pretty fast, but could possibly be even faster.
It's FUD. Freezing of tasks normally takes next to no time. I've never
understood the rediculously long timeout it has. If freezing succeeds, all
processes are frozen within 1/2 a second tops. If it fails, nothing is going
to change in the following 19.5 seconds (or whatever it is if I don't
remember the value properly).
Right. The 20s timeout is again a sign of brokenness.
If we expect something to fail, it should fail immediately, without
waiting for arbitrary timeouts.
And if we don't expect it to fail, why the timeout?
Of course we know it can fail (network problems, etc), so it's wrong
whatever way we look at it.
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Hibernation Redesign
- From: Pavel Machek
- Re: Hibernation Redesign
- From: Rafael J. Wysocki
- Re: Hibernation Redesign
- From: Nigel Cunningham
- Re: Hibernation Redesign
- References:
- Hibernation Redesign (was: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM)
- From: Al Boldi
- Re: Hibernation Redesign
- From: Rafael J. Wysocki
- Re: Hibernation Redesign
- From: Miklos Szeredi
- Re: Hibernation Redesign
- From: Nigel Cunningham
- Hibernation Redesign (was: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM)
- Prev by Date: Re: containers (was Re: -mm merge plans for 2.6.23)
- Next by Date: Re: [EXT4 set 5][PATCH 1/1] expand inode i_extra_isize to support features in larger inode
- Previous by thread: Re: Hibernation Redesign
- Next by thread: Re: Hibernation Redesign
- Index(es):
Relevant Pages
|