linux-kernel - Re: [TuxOnIce-devel] [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]

Message-Id: <1243298544.16743.164.camel@nigel-laptop>
Date:	Tue, 26 May 2009 10:42:24 +1000
From:	Nigel Cunningham <nigel@...onice.net>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	linux-pm@...ts.linux-foundation.org,
	tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@....cz>
Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce

Hi Oliver.

On Tue, 2009-05-26 at 00:45 +0200, Oliver Neukum wrote:
> Am Montag, 25. Mai 2009 23:43:23 schrieb Rafael J. Wysocki:
> > > Oh, before I forget to mention and you ask - how to know what allowance
> > > for the drivers? I use a sysfs entry - the user then just needs to see
> > > what's needed on their first attempt, set up a means of putting that
> > > value in the sysfs file in future (eg /etc/hibernate/tuxonice.conf) and
> > > then forget about it.
> >
> > OK, this is reasonable.
> 
> No, I am afraid it is not. The average user has no clue. Even if that
> is not the problem, the user never knows for sure he has encountered
> the worst case. If you really have drivers that have exceptionally
> large memory requirements (eg. you need to copy video ram), you
> should tell the system through struct driver and do accounting at
> probe and removal of devices.

I'm not suggesting they should expect to know before trying. TuxOnIce
tells you how many were needed in the debugging info printk'd at the end
of a cycle. Add a margin (400 is generally more than adequate) and
you'll have the number you're after:

TuxOnIce debugging info:
- TuxOnIce core  : 3.0.2
- Kernel Version : 2.6.30-rc6
- Compiler vers. : 4.3
- Attempt number : 8
- Parameters     : 0 667656 0 1 0 4
- Overall expected compression percentage: 45.
- Max outstanding reads 1091. Max writes 1089.
  Memory_needed: 1024 x (4096 + 368 + 104) = 4677632 bytes.
  Free mem throttle point reached 0.
- SwapAllocator active.
  Swap available for image: 733753 pages.
- FileAllocator inactive.
- Compressor is 'lzo'.
  Compressed 3215572992 bytes into 1121302124 (65 percent compression).
- I/O speed: Write 119 MB/s, Read 120 MB/s.
- Extra pages    : 832 used/2000.
- Result         : Succeeded.

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/