On Mon, May 07, 2001 at 11:47:34AM -0700, H. Peter Anvin wrote:
> Followup to: <20010505194536.D14127@work.bitmover.com>
> By author: Larry McVoy <lm@bitmover.com>
> In newsgroup: linux.dev.kernel
> >
> > On Sun, May 06, 2001 at 02:20:43PM +1200, Chris Wedgwood wrote:
> > > 1.5GB without ECC? Seems like a disater waiting to happen? Is ECC
> > > memory much more expensive?
> >
> > Almost twice as expensive for 512MB dimms.
> >
> > I used to be a die hard ECC fan but that changed since what we do here is
> > BitKeeper and BitKeeper checksums everything. It tells us right away when
> > we have problems (to date it has found bad memory dimms, NFS corruption,
> > and a SPARC/Linux cache aliasing bug). So I've given up in ECC, we don't
> > need it.
> >
> > On the other hand, if your apps don't have built in integrity checks then
> > ECC is pretty much a requirement.
>
> Isn't this pretty much saying "if you're willing to dedicate your
> system to running nothing but Bitkeeper, you can run it really fast?"
A) Fast has nothing to do with it, ECC runs at the same speed as non-ECC;
B) As I said above, "if your apps don't have built in integrity checks then
ECC is pretty much a requirement";
C) As I said above, we use our systems for BK development, so this choice
makes sense for us.
I think the point you are really missing is that it is not an either/or
choice. All you really need in practice is one application which is
both heavily used and has integrity checks. It could be BitKeeper or
something else, all that matters is that it will detect memory problems.
That application will flush out your memory problems. Yeah, you could
get burned before that app finds them and if you are worried about that,
then run ECC. I think it's an interesting data point, however, that I
care deeply about data integrity and I've transitioned from insisting
on ECC to not caring. If my choice wasn't working for me, I would
still be using ECC. In other words, I'm a lot closer to your way of
thinking than you might expect.
-- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - 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/
This archive was generated by hypermail 2b29 : Mon May 07 2001 - 21:00:25 EST