linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-lkml@crca.org.au>
To: Pavel Machek <pavel@suse.cz>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Chris Friesen <cfriesen@nortel.com>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, Doug Thompson <norsk5@yahoo.com>,
	linux-mm@kvack.org, bluesmoke-devel@lists.sourceforge.net
Subject: Re: marching through all physical memory in software
Date: Sat, 31 Jan 2009 00:00:51 +1100	[thread overview]
Message-ID: <1233320451.11332.13.camel@nigel-laptop> (raw)
In-Reply-To: <20090130091304.GA9495@atrey.karlin.mff.cuni.cz>

Hi again.

On Fri, 2009-01-30 at 10:13 +0100, Pavel Machek wrote:
> > Hi.
> > 
> > On Wed, 2009-01-28 at 20:38 +0100, Pavel Machek wrote:
> > > You can do the scrubbing today by echo reboot > /sys/power/disk; echo
> > > disk > /sys/power/state :-)... or using uswsusp APIs.
> > 
> > That won't work. The RAM retains its contents across a reboot, and even
> > for a little while after powering off.
> 
> Yes, and the original goal was to rewrite all the memory with same
> contents so that parity errors don't accumulate. SO scrubbing here !=
> trying to clear it.

Sorry - I think I missed something.

AFAICS, hibernating is going to be a noop as far as doing anything to
memory that's not touched by the process of hibernating goes. It won't
clear it or scrub it or anything else.

Regards,

Nigel

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-01-30 13:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <497DD8E5.1040305@nortel.com>
     [not found] ` <20090126075957.69b64a2e@infradead.org>
     [not found]   ` <497F5289.404@nortel.com>
2009-01-27 20:16     ` marching through all physical memory in software Eric W. Biederman
2009-01-28 19:38       ` Pavel Machek
2009-01-30  9:05         ` Nigel Cunningham
2009-01-30  9:13           ` Pavel Machek
2009-01-30 13:00             ` Nigel Cunningham [this message]
     [not found]           ` <1236291400.1476.50.camel@dhcp-100-19-198.bos.redhat.com>
2009-03-06 21:16             ` [Patch] mm tracepoints Andrew Morton
     [not found] <715599.77204.qm@web50111.mail.re2.yahoo.com>
2009-01-30 19:32 ` marching through all physical memory in software Eric W. Biederman
2009-01-30 20:20   ` Tim Small
2009-01-31  3:54     ` Eric W. Biederman
2009-01-31 12:48       ` Tim Small
2009-01-31 13:43         ` Henrique de Moraes Holschuh
2009-01-31 21:27           ` Pavel Machek
2009-02-01  1:25             ` Henrique de Moraes Holschuh
2009-01-30 21:10   ` Nigel Cunningham
2009-02-02 18:29   ` Chris Friesen
2009-02-02 22:45     ` Valdis.Kletnieks
2009-02-03 14:31       ` Chris Friesen
2009-02-03 22:25         ` Pavel Machek
2009-02-04 16:03           ` Chris Friesen
2009-02-04 16:47           ` Dave Jiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1233320451.11332.13.camel@nigel-laptop \
    --to=ncunningham-lkml@crca.org.au \
    --cc=arjan@infradead.org \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=cfriesen@nortel.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=norsk5@yahoo.com \
    --cc=pavel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).