linux-kernel - Re: [TuxOnIce-devel] 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 28 Sep 2010 12:34:36 +0200
From:	Martin Steigerwald <Martin@...htvoll.de>
To:	tuxonice-devel@...ts.tuxonice.net
Cc:	Nigel Cunningham <nigel@...onice.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux PM <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"TuxOnIce-devel" <tuxonice-devel@...onice.net>
Subject: Re: [TuxOnIce-devel] Nigel's current for-rafael queue

Am Samstag 25 September 2010 schrieb Nigel Cunningham:
> Hi Rafael.
> 
> 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).
> 
> Results on my Dell XPS M1530, which has an SSD hard drive are:
> 
> With just patch 1 applied:
> Attempt 1: Write 74MB/s; Read 52MB/s
> Attempt 2: Write 68MB/s; Read 52MB/s
> Attempt 3: Write 73MB/s; Read 53MB/s
> 
> With the whole sequence:
> Attempt 1: Write 181MB/s; Read 52MB/s
> Attempt 2: Write 156MB/s; Read 53MB/s
> Attempt 3: Write 160MB/s; Read 52MB/s

Is doesn't get much stabler than 

shambhala:~> grep "PM: Image.*at " /var/log/syslog
Sep 28 11:32:06 shambhala kernel: PM: Image written at 63 MB/s.
Sep 28 11:32:06 shambhala kernel: PM: Image read at 32 MB/s.
Sep 28 11:35:00 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 11:35:00 shambhala kernel: PM: Image read at 32 MB/s.
Sep 28 11:38:43 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 11:38:43 shambhala kernel: PM: Image read at 33 MB/s.
Sep 28 11:41:15 shambhala kernel: PM: Image written at 66 MB/s.
Sep 28 11:41:15 shambhala kernel: PM: Image read at 33 MB/s.
Sep 28 11:42:57 shambhala kernel: PM: Image written at 66 MB/s.
Sep 28 11:42:57 shambhala kernel: PM: Image read at 34 MB/s.
Sep 28 11:45:16 shambhala kernel: PM: Image written at 66 MB/s.
Sep 28 11:45:16 shambhala kernel: PM: Image read at 34 MB/s.
Sep 28 12:19:21 shambhala kernel: PM: Image written at 66 MB/s.
Sep 28 12:19:21 shambhala kernel: PM: Image read at 35 MB/s.
Sep 28 12:21:35 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 12:21:35 shambhala kernel: PM: Image read at 35 MB/s.
Sep 28 12:23:18 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 12:23:18 shambhala kernel: PM: Image read at 35 MB/s.
Sep 28 12:25:23 shambhala kernel: PM: Image written at 64 MB/s.
Sep 28 12:25:23 shambhala kernel: PM: Image read at 36 MB/s.
Sep 28 12:26:55 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 12:26:55 shambhala kernel: PM: Image read at 37 MB/s.
Sep 28 12:28:28 shambhala kernel: PM: Image written at 65 MB/s.
Sep 28 12:28:28 shambhala kernel: PM: Image read at 37 MB/s.

many attempts.

So - without readahead patch for now -

Tested-By: Martin Steigerwald <Martin@...htvoll.de>

on 2.6.36-rc5.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)