linux-kernel - Re: [linux-pm] Nigel's current for-rafael queue

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 26 Sep 2010 07:21:05 +1000
From:	Nigel Cunningham <nigel@...onice.net>
To:	Martin Steigerwald <Martin@...htvoll.de>
CC:	linux-pm@...ts.linux-foundation.org,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	TuxOnIce-devel <tuxonice-devel@...onice.net>
Subject: Re: [linux-pm] Nigel's current for-rafael queue

Hi again.

(I know from your more recent email that you already know the answer to 
this, but others might be interested so I'll reply anyway).

On 26/09/10 01:04, Martin Steigerwald wrote:
> Am Samstag 25 September 2010 schrieb Nigel Cunningham:
>> Hi Rafael.
>
> Hi Nigel,
>
>> Please find attached a slightly updated version of the patchset I sent
>> a few months ago. The main change is that I've prepended and additional
>> patch which lets the user see the speed at which the image is being
>> read and written. This is accomplished by recording the MB/s in a
>> single byte in the image header, and using a couple of __nosavedata
>> variables to get the data back through the atomic restore. I realise
>> the char limits us to 255MB/s at the moment. In future patches, I
>> intend to address this by storing the data in a 'proper' image header
>> (it's a real problem - TuxOnIce reads and writes on the same set up at
>> speeds around 250MB/s).
>
> I like to help by testing these. Is it sufficient to check out your latest
> tuxonice tree, checkout branch for-rafael and switch the hibernate script
> to TryMethod disk.conf?

Yes, that should be sufficient. You do need to be aware (as I said in 
the other reply) that I'm treating this branch like a temporary branch, 
so it's getting rebased and having little modifications made to it. 
Pulling will therefore sometimes require the use of the force option.

Regards,

Nigel
--
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/