From: Andi Kleen <andi@firstfloor.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Russ Anderson <rja@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: Re: [PATCH 1/2] Avoid putting a bad page back on the LRU
Date: Wed, 08 Apr 2009 08:46:41 +0200 [thread overview]
Message-ID: <87r603abhq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200904080543.16454.ioe-lkml@rameria.de> (Ingo Oeser's message of "Wed, 8 Apr 2009 05:43:15 +0200")
Ingo Oeser <ioe-lkml@rameria.de> writes:
>
> Clearing the flag doesn't change the fact, that this page is representing
> permanently bad RAM.
Yes, you cannot ever clear a Poison flag, at least not without a special
hardware mechanism that clears the hardware poison too (but that has
other issues in Linux too). Otherwise you would die later.
> What about removing it from the LRU and adding it to a bad RAM list in every case?
That is what memory_failure() already should be doing. Except there's no list
currently.
> After hot swapping the physical RAM banks it could be moved back, not before.
Linux doesn't really support that. That is at least not when it's OS visible.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
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 prev parent reply other threads:[~2009-04-08 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 0:11 Russ Anderson
2009-04-08 3:43 ` Ingo Oeser
2009-04-08 6:46 ` Andi Kleen [this message]
2009-04-08 13:31 ` Russ Anderson
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=87r603abhq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rja@sgi.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox