[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1I96uz-0005Bl-00@dorka.pomaz.szeredi.hu>
Date: Fri, 13 Jul 2007 00:13:49 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: pavel@....cz
CC: miklos@...redi.hu, nigel@...el.suspend2.net, rjw@...k.pl,
a1426z@...ab.com, jeremy@...p.org, jbms@....edu,
nickpiggin@...oo.com.au, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org
Subject: Re: Hibernation Redesign
> > > > 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.
>
> Well, "scenario 1/2 - simple/tricky deadlock" is a sign of brokenness,
> too.
Sure. But that one hasn't generated a single bug report (and never
will), because it's so insanely difficult to produce, even if one
explicitly wants to do that. It will just never happen accidentally.
And even if it happens, there's absolutely no side affects on the rest
of the system. You managed to make a process not react to SIGKILL,
well hurray. You can do that more easily with ptrace().
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists