On Thu, May 7, 2009 at 5:09 AM, Pavel Machek <pavel@xxxxxx> wrote:
Really? Last time I used it, it was dog slow to suspend and dog slow to resume. And threw away most of my useful stuff, making my system slow after resume. I could as well have restarted and be fully functional in much less time.
We need a competitor to swsusp in kernel so that you can get you off your a$$ and make the swsusp better.
What is out of tree? People just install the patch and use it instead of in-kernel version. Isn't that shameful enough for you to keep quiet?
which went where?
Do you have data to support which one is used more?
Hi!
> I'd like to submit TuxOnIce for review, with a view to seeking to get it
> merged, perhaps in 2.6.31 or .32 (depending upon what needs work before
> it can be merged) and the willingness of those who matter.
>
> To briefly summarise the advantages to merging TuxOnIce:
>
> - Support for multiple swap devices
> - Support for non-swap (an ordinary file can be used)
> - Uses cryptoapi (LZO support, more than 2x speed of uncompressed data!)
> - Asynchronous I/O, readahead, multithreaded. Get the maximum throughput
> possible with your hardware.
> - Userspace user interface that lets you abort hibernating and abort
> resuming, get nice progress display etc.
All these are either done by uswsusp already, or could be done w/o
modifying kernel code.
Really? Last time I used it, it was dog slow to suspend and dog slow to resume. And threw away most of my useful stuff, making my system slow after resume. I could as well have restarted and be fully functional in much less time.
We need a competitor to swsusp in kernel so that you can get you off your a$$ and make the swsusp better.
> - 8 years of testing and improvement.
Yeah, 8 years of out of tree testing; while current code is used by
basically every distro out there.
What is out of tree? People just install the patch and use it instead of in-kernel version. Isn't that shameful enough for you to keep quiet?
> - Full image of memory (LRU pages that don't need to be atomically
> copied are saved prior to the atomic copy, then used as the
> destination of the atomic copy).
Yeah, that was the patch that did not go in
> - Support for resuming a different image after writing an image - makes
> powering down a UPS after writing an image doable.
This can be done w/o kernel code. Someone had a patch...
which went where?
> - Simple to set up (works without any userspace binaries, uses existing
> resume= and noresume commandline parameters).
Given that distros ship uswsusp already... is that really an advantage.
To summarise disadvantages:
- only core has 8000 LoC
- it does stuff that can be easily done in userspace
(and that todays distros _do_ in userspace).
- it duplicates uswsusp functionality.
- compared to [u]swsusp, it received little testing
Do you have data to support which one is used more?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel@xxxxxxxxxxxxxxxxxx
http://lists.tuxonice.net/mailman/listinfo/tuxonice-devel
_______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
