public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Jones <davej@codemonkey.org.uk>
Cc: boissiere@adiglobal.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [STATUS 2.5]  October 30, 2002
Date: 30 Oct 2002 23:22:12 -0700	[thread overview]
Message-ID: <m1iszjgmaz.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20021030161708.GA8321@suse.de>

Dave Jones <davej@codemonkey.org.uk> writes:

> Something else I took a look at in the last few days was the ECC
> drivers. These are also zero impact, and could go in after the freeze
> (assuming the authors want them merged). They could do with a small
> amount of cleanup, but otherwise look ok.

Assuming they work.  No offense to the guys who got the ball rolling, but
the architecture is lousy, and every driver I have messed with does not
work correctly, and I wind up reimplementing it before I can use it.

I actually like the idea of ECC drivers, and routinely make certain
there is a working ECC driver on the systems I ship.  It is so much
very easier to catch memory errors with good ECC error reporting.  But
unless I have slept soundly through a fundamental change, the
linux-ecc project currently does not ship quality drivers.  The
infrastructure is bad, and the code is not quite correct. 

If you want I can dig up the drivers I am currently using and send
them to you.

I even have a working memory scrub routine.

Eric

  parent reply	other threads:[~2002-10-31  6:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 16:17 [STATUS 2.5] October 30, 2002 Dave Jones
2002-10-30 17:14 ` Randy.Dunlap
2002-10-31  6:22 ` Eric W. Biederman [this message]
2002-10-31 10:56   ` Alan Cox
2002-10-31 16:30     ` Randy.Dunlap
2002-10-31 14:40   ` Dave Jones
2002-10-31 23:01   ` Pavel Machek
2002-11-01 14:05     ` Eric W. Biederman
2002-11-01 16:49       ` Alan Cox
2002-11-01 17:00         ` Richard B. Johnson
2002-11-02 12:19           ` Eric W. Biederman
2002-11-04 14:31             ` Richard B. Johnson
2002-11-04 15:58               ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 17:14 Ed Vance
2002-11-01 22:25 Ed Vance
2002-11-02  0:33 ` Werner Almesberger
2002-11-01 19:14 Ken Ryan
2002-11-01 19:56 ` Richard B. Johnson
2002-11-01 21:27   ` Ken Ryan
2002-11-01 18:17 Ed Vance
2002-11-01 18:46 ` Malcolm Beattie
2002-10-30 15:13 Guillaume Boissiere
2002-10-30 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-30 22:36   ` David S. Miller
2002-10-31  2:48     ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31  2:44       ` David S. Miller
2002-10-31  3:07         ` kuznet
2002-10-31  3:16         ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31  3:13           ` David S. Miller

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=m1iszjgmaz.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=boissiere@adiglobal.com \
    --cc=davej@codemonkey.org.uk \
    --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