linux-kernel - Re: [RFC] TuxOnIce

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 May 2009 19:42:54 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Nigel Cunningham <nigel@...onice.net>,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	tuxonice-devel@...ts.tuxonice.net
Subject: Re: [RFC] TuxOnIce

On Thursday 07 May 2009, Pavel Machek wrote:
> 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.
> 
> > - 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.
> 
> > - 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...
> 
> > - 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

Actually, I see advantages of working together versus fighting flame wars.
Please stop that, I'm not going to take part in it this time.

Best,
Rafael
--
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/