From: Werner Almesberger <wa@almesberger.net>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Richard B. Johnson'" <root@chaos.analogic.com>,
Ken Ryan <newsryan@leesburg-geeks.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [STATUS 2.5] October 30, 2002
Date: Fri, 1 Nov 2002 21:33:25 -0300 [thread overview]
Message-ID: <20021101213324.H2599@almesberger.net> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A33C8E@EXCHANGE>; from EdV@macrolink.com on Fri, Nov 01, 2002 at 02:25:55PM -0800
Ed Vance wrote:
> functional as long as he can keep up. For the memory, the many separate bit
> error events would cause only correctable errors, as long as the scrubbing
> can keep up.
Don't those bit errors have a Poissonian character ? If so, it's
impossible to "keep up". All you can do is make the interval small
enough that, on average, it takes a long time until you get hit
twice (or more often) in that interval.
A better example would be car tires on roads with many randomly
distributed sharp objects (i.e. such that age does not significantly
change the odds of tire damage): you can keep going as long as you
can get a flat tire fixed before another tire gets punctured. But
sometimes, you may end up with two flat tires, and need a tow truck.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-11-02 0:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 22:25 [STATUS 2.5] October 30, 2002 Ed Vance
2002-11-02 0:33 ` Werner Almesberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 17:14 Ed Vance
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 16:17 Dave Jones
2002-10-30 17:14 ` Randy.Dunlap
2002-10-31 6:22 ` Eric W. Biederman
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
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=20021101213324.H2599@almesberger.net \
--to=wa@almesberger.net \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=newsryan@leesburg-geeks.org \
--cc=root@chaos.analogic.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.