All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Stefan Assmann <sassmann@kpanic.de>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, tony.luck@intel.com,
	andi@firstfloor.org, mingo@elte.hu, rick@vanrein.org,
	rdunlap@xenotime.net
Subject: Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)
Date: Thu, 23 Jun 2011 09:30:37 -0700	[thread overview]
Message-ID: <4E036A2D.1060402@zytor.com> (raw)
In-Reply-To: <4E035DD1.1030603@kpanic.de>

On 06/23/2011 08:37 AM, Stefan Assmann wrote:
> 
> According to Rick's reply in this thread a damaged row in a DIMM can
> easily cause a few thousand entries in the e820 table because it doesn't
> handle patterns. So the question I'm asking is, is it acceptable to
> have an e820 table with thousands maybe ten-thousands of entries?
> I really have no idea of the implications, maybe somebody else can
> comment on that.
> 

Given that that is what actually ends up happening in the kernel at some
point anyway, I don't see why it would matter.

The bubble sort has to go, but quite frankly stress-testing the range
handling isn't a bad thing.
	
	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Stefan Assmann <sassmann@kpanic.de>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, tony.luck@intel.com,
	andi@firstfloor.org, mingo@elte.hu, rick@vanrein.org,
	rdunlap@xenotime.net
Subject: Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)
Date: Thu, 23 Jun 2011 09:30:37 -0700	[thread overview]
Message-ID: <4E036A2D.1060402@zytor.com> (raw)
In-Reply-To: <4E035DD1.1030603@kpanic.de>

On 06/23/2011 08:37 AM, Stefan Assmann wrote:
> 
> According to Rick's reply in this thread a damaged row in a DIMM can
> easily cause a few thousand entries in the e820 table because it doesn't
> handle patterns. So the question I'm asking is, is it acceptable to
> have an e820 table with thousands maybe ten-thousands of entries?
> I really have no idea of the implications, maybe somebody else can
> comment on that.
> 

Given that that is what actually ends up happening in the kernel at some
point anyway, I don't see why it would matter.

The bubble sort has to go, but quite frankly stress-testing the range
handling isn't a bad thing.
	
	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-06-23 16:31 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 11:18 [PATCH v2 0/3] support for broken memory modules (BadRAM) Stefan Assmann
2011-06-22 11:18 ` Stefan Assmann
2011-06-22 11:18 ` [PATCH v2 1/3] Add string parsing function get_next_ulong Stefan Assmann
2011-06-22 11:18   ` Stefan Assmann
2011-06-22 11:18 ` [PATCH v2 2/3] support for broken memory modules (BadRAM) Stefan Assmann
2011-06-22 11:18   ` Stefan Assmann
2011-06-22 11:18 ` [PATCH v2 3/3] Add documentation and credits for BadRAM Stefan Assmann
2011-06-22 11:18   ` Stefan Assmann
2011-06-22 18:00 ` [PATCH v2 0/3] support for broken memory modules (BadRAM) Andrew Morton
2011-06-22 18:00   ` Andrew Morton
2011-06-22 18:06   ` Josh Boyer
2011-06-22 18:06     ` Josh Boyer
2011-06-22 18:09   ` Randy Dunlap
2011-06-22 18:09     ` Randy Dunlap
2011-06-22 18:11     ` Nancy Yuen
2011-06-22 18:11       ` Nancy Yuen
2011-06-22 18:13   ` H. Peter Anvin
2011-06-22 18:13     ` H. Peter Anvin
2011-06-22 19:01     ` Nancy Yuen
2011-06-22 19:01       ` Nancy Yuen
2011-06-22 19:06       ` H. Peter Anvin
2011-06-22 19:06         ` H. Peter Anvin
2011-06-22 18:24   ` Andi Kleen
2011-06-22 18:24     ` Andi Kleen
2011-06-22 18:38     ` Andrew Morton
2011-06-22 18:38       ` Andrew Morton
2011-06-22 18:56       ` Andi Kleen
2011-06-22 18:56         ` Andi Kleen
2011-06-22 19:05         ` H. Peter Anvin
2011-06-22 19:05           ` H. Peter Anvin
2011-06-22 19:15           ` Andi Kleen
2011-06-22 19:15             ` Andi Kleen
2011-06-22 20:25             ` H. Peter Anvin
2011-06-22 20:25               ` H. Peter Anvin
2011-06-22 20:28               ` Andi Kleen
2011-06-22 20:28                 ` Andi Kleen
2011-06-22 19:46   ` [PATCH] x86: e820: Eliminate bubble sort from sanitize_e820_map Mike Ditto
2011-06-22 19:46     ` Mike Ditto
2011-06-22 20:18   ` [PATCH v2 0/3] support for broken memory modules (BadRAM) Stefan Assmann
2011-06-22 20:18     ` Stefan Assmann
2011-06-23 10:10   ` Rick van Rein
2011-06-23 10:10     ` Rick van Rein
2011-06-22 18:15 ` H. Peter Anvin
2011-06-22 18:15   ` H. Peter Anvin
2011-06-22 20:30   ` Stefan Assmann
2011-06-22 20:30     ` Stefan Assmann
2011-06-22 20:33     ` H. Peter Anvin
2011-06-22 20:33       ` H. Peter Anvin
2011-06-23 10:33   ` Rick van Rein
2011-06-23 10:33     ` Rick van Rein
2011-06-23 10:49     ` Rick van Rein
2011-06-23 10:49       ` Rick van Rein
2011-06-23 13:39 ` Matthew Garrett
2011-06-23 13:39   ` Matthew Garrett
2011-06-23 14:08   ` Stefan Assmann
2011-06-23 14:08     ` Stefan Assmann
2011-06-23 14:12     ` Matthew Garrett
2011-06-23 14:12       ` Matthew Garrett
2011-06-23 15:37       ` Stefan Assmann
2011-06-23 15:37         ` Stefan Assmann
2011-06-23 16:30         ` H. Peter Anvin [this message]
2011-06-23 16:30           ` H. Peter Anvin
2011-06-24  0:59           ` Andi Kleen
2011-06-24  0:59             ` Andi Kleen
2011-06-23 17:00         ` Andi Kleen
2011-06-23 17:00           ` Andi Kleen
2011-06-23 17:12           ` Luck, Tony
2011-06-23 17:12             ` Luck, Tony
2011-06-24  1:03             ` Craig Bergstrom
2011-06-24  1:08               ` Andi Kleen
2011-06-24  1:08                 ` Andi Kleen
2011-06-24  1:22                 ` Craig Bergstrom
2011-06-24  1:22                   ` Craig Bergstrom
2011-06-24  8:05               ` Rick van Rein
2011-06-24  8:05                 ` Rick van Rein
2011-06-24 14:34                 ` Craig Bergstrom
2011-06-24 14:35                 ` Craig Bergstrom
2011-06-24 16:16                 ` H. Peter Anvin
2011-06-24 16:16                   ` H. Peter Anvin
2011-06-24 16:40                   ` Luck, Tony
2011-06-24 16:40                     ` Luck, Tony
2011-06-24 16:56                     ` Rick van Rein
2011-06-24 16:56                       ` Rick van Rein
2011-06-24 17:14                       ` H. Peter Anvin
2011-06-24 17:14                         ` H. Peter Anvin
2011-06-24  1:09             ` Craig Bergstrom
     [not found] <fa.fHPNPTsllvyE/7DxrKwiwgVbVww@ifi.uio.no>
2011-06-24 21:10 ` Shane Nay
2011-06-24 21:10   ` Shane Nay
2011-06-28  2:33   ` Craig Bergstrom
2011-06-28  2:33     ` Craig Bergstrom
2011-06-29  8:08     ` Rick van Rein
2011-06-29  8:08       ` Rick van Rein
2011-06-29 15:28       ` craig lkml
2011-06-29 16:06         ` Craig Bergstrom
2011-06-29 16:06           ` Craig Bergstrom
2011-06-29 21:24           ` Tony Luck
2011-06-29 21:24             ` Tony Luck
2011-06-29 15:29       ` craig lkml
2011-06-30 14:32       ` Jody Belka
2011-06-30 14:32         ` Jody Belka
  -- strict thread matches above, loose matches on Subject: below --
2011-06-21  9:23 Stefan Assmann
2011-06-21 22:02 ` Andrew Morton
2011-06-22 11:11   ` Stefan Assmann

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=4E036A2D.1060402@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=rdunlap@xenotime.net \
    --cc=rick@vanrein.org \
    --cc=sassmann@kpanic.de \
    --cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.