From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id CF3146B00E8 for ; Wed, 29 Jun 2011 11:28:30 -0400 (EDT) Received: by vxg38 with SMTP id 38so1398824vxg.14 for ; Wed, 29 Jun 2011 08:28:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20110629080827.GA975@phantom.vanrein.org> References: <532cc290-4b9c-4eb2-91d4-aa66c01bb3a0@glegroupsg2000goo.googlegroups.com> <20110629080827.GA975@phantom.vanrein.org> Date: Wed, 29 Jun 2011 08:28:26 -0700 Message-ID: Subject: Re: [PATCH v2 0/3] support for broken memory modules (BadRAM) From: craig lkml Content-Type: multipart/alternative; boundary=bcaec501665b9626c704a6db6f94 Sender: owner-linux-mm@kvack.org List-ID: To: Rick van Rein Cc: Craig Bergstrom , fa.linux.kernel@googlegroups.com, "H. Peter Anvin" , Stefan Assmann , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "akpm@linux-foundation.org" , "Luck, Tony" , Andi Kleen , "mingo@elte.hu" , "rdunlap@xenotime.net" , Nancy Yuen , Michael Ditto --bcaec501665b9626c704a6db6f94 Content-Type: text/plain; charset=ISO-8859-1 Hi Rick, Thanks for your response. My sincere apologies for not posting the work directly. My intention is to point interested parties to contributions that Google has made to this space through known and respected channels. The cited research is not my research but the research of my colleagues. As a result, I hesitate to paraphrase the work as I will likely get the details wrong. In any case, Shane's points are the most relevant for the discussion here. Please refer to his post in this thread. In an attempt to contribute to the community as much as I can, I have prepared and mailed our BadRAM patch as requested. In case it is not otherwise clear, my belief is that the ideal solution for the upstream kernel is a hybrid of our approaches. Thank you, CraigB On Wed, Jun 29, 2011 at 1:08 AM, Rick van Rein wrote: > Hello Craig, > > > Some folks had mentioned that they're interested in details about what > > we've learned about bad ram from our fleet of machines. I suspect > > that you need ACM portal access to read this, > > I'm happy that this didn't cause a flame, but clearly this is not the > right response in an open environment. ACM may have copyright on the > *form* in which you present your knowledge, but could you please poor > the knowledge in another form that bypasses their copyright so the > knowledge is made available to all? > > > Thanks, > -Rick > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > --bcaec501665b9626c704a6db6f94 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Rick,

Thanks for your response. =A0My sincere apologi= es for not posting the work directly.

My intention= is to point interested parties to contributions that Google has made to th= is space through known and respected channels. =A0The cited research is not= my research but the research of my=A0colleagues. =A0As a result, I hesitat= e to paraphrase the work as I will likely get the details wrong. =A0In any = case, Shane's points are the most relevant for the discussion here. =A0= Please refer to his post in this thread.

In an attempt to contribute to the community as much as= I can, I have prepared and mailed our BadRAM patch as requested. =A0In cas= e it is not otherwise clear, my belief is that the ideal solution for the u= pstream kernel is a hybrid of our approaches.

Thank you,
CraigB

On Wed, Jun 29, 2011 at 1:08 AM, Rick van Rein <= ;rick@vanrein.org> wrote:=
Hello Craig,

> Some folks had mentioned that they're interested in details about = what
> we've learned about bad ram from our fleet of machines. =A0I suspe= ct
> that you need ACM portal access to read this,

I'm happy that this didn't cause a flame, but clearly this is= not the
right response in an open environment. =A0ACM may have copyright on the
*form* in which you present your knowledge, but could you please poor
the knowledge in another form that bypasses their copyright so the
knowledge is made available to all?


Thanks,
=A0-Rick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel= " in
the body of a message to majordomo@vger.kernel.org
More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
Please read the FAQ at =A0http://www.tux.org/lkml/

--bcaec501665b9626c704a6db6f94-- -- 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: email@kvack.org