[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <987664A83D2D224EAE907B061CE93D5301E938F2FD@orsmsx505.amr.corp.intel.com>
Date: Thu, 23 Jun 2011 10:12:55 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: Andi Kleen <andi@...stfloor.org>,
Stefan Assmann <sassmann@...nic.de>
CC: Matthew Garrett <mjg59@...f.ucam.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mingo@...e.hu" <mingo@...e.hu>, "hpa@...or.com" <hpa@...or.com>,
"rick@...rein.org" <rick@...rein.org>,
"rdunlap@...otime.net" <rdunlap@...otime.net>
Subject: RE: [PATCH v2 0/3] support for broken memory modules (BadRAM)
> I don't think it makes sense to handle something like that with a list.
> The compact representation currently in badram is great for that.
I'd tend to agree here. Rick has made a convincing argument that there
are significant numbers of real world cases where a defective row/column
in a DIMM results in a predictable pattern of errors. The ball is now
in Google's court to take a look at their systems that have high numbers
of errors to see if they can actually be described by a small number
of BadRAM patterns as Rick has claimed.
-Tony
--
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/
Powered by blists - more mailing lists