Re: [PATCH 0/2] Migrate data off physical pages with corrected memory errors (Version 7)
From: Andi Kleen
Date: Mon Jul 21 2008 - 15:40:29 EST
On Sun, Jul 20, 2008 at 12:39:14PM -0500, Russ Anderson wrote:
> The patch has a module for IA64, based on experience on IA64 hardware.
> It is a first step, to get the basic functionality in the kernel.
The basic functionality doesn't seem flexible enough for me
for useful policies.
> (~20,000 in one customer system). So disabling the memory on a
> DIMM with a flaky connector is a small percentage of overall memory.
> On a large NUMA machine the flaky DIMM connector would only effect
> memory on one node.
You would still lose significant parts of that node, won't you?
Even on the large systems people might miss a node or two.
> A good enhancement would be to migrate all the data off a DRAM and/or
> DIMM when a threshold is exceeded. That would take knowledge of the
> physical memory to memory map layout.
Would be probably difficult to teach this the kernel in a nice generic
way. In particular interleaving is difficult.
> > If you really wanted to do this you probably should hook it up
> > to mcelog's (or the IA64 equivalent) DIMM database
> Is there an IA64 equivalent? I've looked at the x86_64 mcelog,
> but have not found a IA64 version.
There's a sal logger process in user space I believe, but I have never looked
at it. It could do these things in theory.
Also in the IA64 case the firmware can actually tell the kernel
what to do because it gets involved here (and firmware often
has usable heuristics for this case)
> > and DIMM specific knowledge. But it's unlikely it can be really
> > done nicely in a way that is isolated from very specific
> > knowledge about the underlying memory configuration.
> Agreed. An interface to export the physical memory configuration
> (from ACPI tables?) would be useful.
On x86 there's currently only DMI/SMBIOS for this, but it has some issues.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/