From: Tim Small <tim@buttersideup.com>
To: bluesmoke-devel@lists.sourceforge.net, linux-mm@kvack.org
Subject: Failing memory auto-hotremove support?
Date: Thu, 03 Jul 2008 13:25:23 +0100 [thread overview]
Message-ID: <486CC533.6080302@buttersideup.com> (raw)
Hello,
I just noticed that there is memory hotplug / hotremove support in the
kernel.org kernel now.
I was thinking that it may be desirable (e.g. on large NUMA systems) to
automatically trigger the removal of memory modules (or just take a
section of the memory module out of use, if applicable), if a memory
module exceeded a pre-set correctable error rate (or RIGHT-NOW, if an
uncorrectable memory error was detected).
Tim.
--
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>
next reply other threads:[~2008-07-03 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 12:25 Tim Small [this message]
2008-07-03 17:42 ` Doug Thompson
2008-07-04 5:24 ` Yasunori Goto
2008-07-09 23:34 ` Badari Pulavarty
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=486CC533.6080302@buttersideup.com \
--to=tim@buttersideup.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox