public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Nick Piggin <npiggin@suse.de>, Andi Kleen <andi@firstfloor.org>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, fengguang.wu@intel.com,
	hidehiro.kawai.ez@hitachi.com, linux-arch@vger.kernel.org
Subject: Re: [PATCH] [11/19] HWPOISON: Refactor truncate to allow direct truncating of page v2
Date: Thu, 6 Aug 2009 14:04:17 +0200	[thread overview]
Message-ID: <20090806120417.GC22124@basil.fritz.box> (raw)
In-Reply-To: <20090806134830.4f3931d2@skybase>

> This is not relevant for s390, as current machines do transparent memory
> sparing if a memory module goes bad. Really old machines reported bad
> memory to the OS by means of a machine check (storage error uncorrected
> and storage error corrected). I have never seen this happen, the level
> below the OS deals with these errors for us.

Ok fine. It's for the poorer cousins then who can't afford memory mirroring.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2009-08-06 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200908051136.682859934@firstfloor.org>
     [not found] ` <20090805093638.D3754B15D8@basil.firstfloor.org>
     [not found]   ` <20090805102008.GB17190@wotan.suse.de>
     [not found]     ` <20090805134607.GH11385@basil.fritz.box>
     [not found]       ` <20090805140145.GB28563@wotan.suse.de>
     [not found]         ` <20090805141001.GJ11385@basil.fritz.box>
2009-08-05 14:16           ` [PATCH] [11/19] HWPOISON: Refactor truncate to allow direct truncating of page v2 Nick Piggin
2009-08-05 14:16             ` Nick Piggin
2009-08-05 14:41             ` Andi Kleen
2009-08-05 14:44               ` Nick Piggin
2009-08-05 15:00               ` Matthew Wilcox
2009-08-06 11:48             ` Martin Schwidefsky
2009-08-06 12:04               ` Andi Kleen [this message]

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=20090806120417.GC22124@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=schwidefsky@de.ibm.com \
    /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