public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rick van Rein <rick@vanrein.org>
To: Rick van Rein <rick@vanrein.org>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Date: Sun, 2 Mar 2008 19:34:16 +0000	[thread overview]
Message-ID: <20080302193416.GA27780@phantom.vanrein.org> (raw)
In-Reply-To: <20080302175326.GB32381@nineveh.local>

Hello,

> This is a great feature for those of us who value their money more
> than a few hours of time as well.  :-)

That's how it's most often used, indeed.  I do value the environmental
aspect as well: the potential for memory manufacturers (say, for the
$100 laptop) to ship out their broken memories at a low cost, thereby
delivering more products for a given amount of toxic waste created in
the chip etching process.

> I would very much like to see this patch in mainline

Many, many people want to.  I've been asked about it a lot, but always
lacked the time to figure out how.

> ISTR that one
> argument that has been historically made against this sort of thing is
> that it would make bug reports unreliable.

Actually it's broken memory that makes reports unreliable, not the patch :)

After the right set of broken addresses has been applied, the whole system
runs as reliably as any other system.  And I hope people have the wits to
mistrust a system for a while after they've plugged in broken DIMMs ;-)

> mechanism now, so that shouldn't be a showstopper -- if that's the
> only argument, then set a new taint flag, please.

I doubt that'll be necessary, but yes, it'd be a way out.  Thanks.

Cheers,
 -Rick

  reply	other threads:[~2008-03-02 19:34 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 13:42 [PATCH 2.6.24] mm: BadRAM support for broken memory Rick van Rein
2008-03-02 17:01 ` KOSAKI Motohiro
2008-03-02 17:42   ` Rick van Rein
2008-03-03  3:21     ` KOSAKI Motohiro
2008-03-03  5:32   ` Nick Piggin
2008-03-03  7:14     ` KOSAKI Motohiro
2008-03-03  7:35       ` Nick Piggin
2008-03-03  9:49         ` KOSAKI Motohiro
2008-03-03  9:58         ` KAMEZAWA Hiroyuki
2008-03-02 17:53 ` Joseph Fannin
2008-03-02 19:34   ` Rick van Rein [this message]
2008-03-03 14:14 ` Pavel Machek
2008-03-03 16:41   ` KOSAKI Motohiro
2008-03-08 10:25     ` H. Peter Anvin
2008-03-08 10:30       ` H. Peter Anvin
2008-03-03 17:38 ` Randy Dunlap
     [not found] ` <20080303082238.GB13580@elte.hu>
     [not found]   ` <47CC3005.5090706@zytor.com>
     [not found]     ` <20080304133028.GC32383@elte.hu>
2008-03-04 16:29       ` H. Peter Anvin
2008-03-04 16:47         ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-03-04 12:21 devzero
2008-03-04 13:27 ` Ingo Molnar
2008-03-04 13:43   ` Rick van Rein
2008-03-04 14:06     ` Ingo Molnar
2008-03-04 15:05     ` Pavel Machek
2008-03-08 10:27   ` H. Peter Anvin
2008-03-08 11:13     ` Jiri Kosina
2008-03-10 10:12       ` Jan-Simon Möller
2008-03-10 11:24         ` Jan-Simon Möller
2008-03-10 11:52           ` Pavel Machek
2008-03-10 14:23             ` Jan-Simon Möller
2008-03-10 17:20               ` H. Peter Anvin
2008-03-10 17:48                 ` Jan-Simon Möller
2008-03-10 18:59                 ` Jan-Simon Möller
2008-03-10 19:16                   ` Jan-Simon Möller
2008-03-10 22:56                   ` Pavel Machek
2008-03-11  0:37                     ` Jan-Simon Möller
2008-03-11 17:23                   ` Len Brown
2008-03-11 17:49                     ` Jan-Simon Möller
2008-03-11 19:24                       ` Johannes Weiner
2008-03-11 20:00                         ` Jan-Simon Möller
2008-03-10 22:07                 ` Rick van Rein
2008-03-11  0:41                 ` Jan-Simon Möller
2008-03-11  6:41                   ` H. Peter Anvin
2008-03-04 14:00 devzero

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=20080302193416.GA27780@phantom.vanrein.org \
    --to=rick@vanrein.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.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