Messages in this thread |  | | | Date | Thu, 6 Oct 2005 00:44:18 +0200 | | From | Pavel Machek <> | | Subject | Re: [swsusp] separate snapshot functionality to separate file |
| |
Hi!
> >>Pavel, at the PM summit, we agreed to work toward getting Suspend2 > >>merged. I've been working since then on cleaning up the code, splitting > >>the patches up nicely and so on. In the meantime, you seem to have gone > >>off on a completely different tangent, going right against what we > >>agreed then. > >Sorry about that. At pm summit, I did not know if uswsusp was > >feasible. Now I'm pretty sure it is (code works and is stable). > > Ok, excuse me for butting in. > > I would just like to give the point of view of a user. > > I have been using suspend2 probably at least once a day for about a year > now, and I love it. I have had zero cases of data corruption, and it's > fast, effective, and reliable. I can't say the same about the in-kernel > swsusp. When I tried it (once), a few months ago: > > - It was dog slow because it doesn't use compression > - Even though it's dog slow, it doesn't save all RAM > - Therefore the machine is dog slow after resume > - It doesn't have a decent UI > - There is no way to abort suspend once it's started. (Whatever others > may say, this /is/ useful, especially when you've forgotten something > and you're in a hurry and don't have two more minutes to waste waiting > for a suspend/resume cycle.)
With uswsusp (aka swsusp3), you can do all this in userland. Stop whining, start hacking... Code is at kernel.org/git/.../linux-sw3.
Pavel -- if you have sharp zaurus hardware you don't need... you know my address - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |