From: Arjan van de Ven <arjan@infradead.org>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: marching through all physical memory in software
Date: Mon, 26 Jan 2009 07:59:57 -0800 [thread overview]
Message-ID: <20090126075957.69b64a2e@infradead.org> (raw)
In-Reply-To: <497DD8E5.1040305@nortel.com>
On Mon, 26 Jan 2009 09:38:13 -0600
"Chris Friesen" <cfriesen@nortel.com> wrote:
> Someone is asking me about the feasability of "scrubbing" system
> memory by accessing each page and handling the ECC faults.
>
Hi,
I would suggest that you look at the "edac" subsystem, which tries to
do exactly this....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-01-26 16:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 15:38 marching through all physical memory in software Chris Friesen
2009-01-26 15:59 ` Arjan van de Ven [this message]
2009-01-27 18:29 ` Chris Friesen
2009-01-27 20:16 ` Eric W. Biederman
2009-01-27 20:16 ` Eric W. Biederman
2009-01-28 19:38 ` Pavel Machek
2009-01-28 19:38 ` Pavel Machek
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:13 ` Pavel Machek
2009-01-30 9:13 ` Pavel Machek
2009-01-30 13:00 ` Nigel Cunningham
2009-01-30 13:00 ` Nigel Cunningham
2009-03-05 22:16 ` [Patch] mm tracepoints Larry Woodman
2009-03-06 2:11 ` KOSAKI Motohiro
2009-03-06 2:26 ` Steven Rostedt
2009-03-06 11:04 ` Ingo Molnar
2009-03-06 12:33 ` Larry Woodman
2009-03-06 13:55 ` Ingo Molnar
2009-03-06 16:57 ` Larry Woodman
2009-03-06 17:10 ` Ingo Molnar
2009-03-06 17:38 ` Peter Zijlstra
2009-03-06 17:46 ` Ingo Molnar
2009-03-06 17:56 ` Peter Zijlstra
2009-03-06 18:01 ` Ingo Molnar
2009-03-06 18:20 ` Peter Zijlstra
2009-03-06 18:24 ` Ingo Molnar
2009-03-06 20:01 ` Larry Woodman
2009-03-06 19:06 ` Larry Woodman
2009-03-06 21:53 ` Chris Friesen
2009-03-06 19:22 ` Larry Woodman
2009-03-25 18:09 ` Latest mm tracepoints patch merged to your tip tree Larry Woodman
2009-03-06 21:16 ` [Patch] mm tracepoints Andrew Morton
2009-03-06 21:16 ` Andrew Morton
2009-02-06 9:00 ` marching through all physical memory in software Andi Kleen
2009-02-07 3:03 ` Henrique de Moraes Holschuh
[not found] <715599.77204.qm@web50111.mail.re2.yahoo.com>
2009-01-30 19:32 ` Eric W. Biederman
2009-01-30 19:32 ` Eric W. Biederman
2009-01-30 20:20 ` Tim Small
2009-01-30 20:20 ` Tim Small
2009-01-31 3:54 ` Eric W. Biederman
2009-01-31 3:54 ` Eric W. Biederman
2009-01-31 12:48 ` Tim Small
2009-01-31 12:48 ` Tim Small
2009-01-31 13:43 ` Henrique de Moraes Holschuh
2009-01-31 13:43 ` Henrique de Moraes Holschuh
2009-01-31 21:27 ` Pavel Machek
2009-01-31 21:27 ` Pavel Machek
2009-02-01 1:25 ` Henrique de Moraes Holschuh
2009-02-01 1:25 ` Henrique de Moraes Holschuh
2009-01-30 21:10 ` Nigel Cunningham
2009-01-30 21:10 ` Nigel Cunningham
2009-02-02 18:29 ` Chris Friesen
2009-02-02 18:29 ` Chris Friesen
2009-02-02 22:45 ` Valdis.Kletnieks
2009-02-03 14:31 ` Chris Friesen
2009-02-03 14:31 ` Chris Friesen
2009-02-03 22:25 ` Pavel Machek
2009-02-03 22:25 ` Pavel Machek
2009-02-04 16:03 ` Chris Friesen
2009-02-04 16:03 ` Chris Friesen
2009-02-04 16:47 ` Dave Jiang
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=20090126075957.69b64a2e@infradead.org \
--to=arjan@infradead.org \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.