From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] pineview atom
Date: Thu, 18 Feb 2010 15:27:24 -0800 [thread overview]
Message-ID: <13426df11002181527tf091fbek49420d9a074614e7@mail.gmail.com> (raw)
In-Reply-To: <166806221002181512x13dc3662jf5b3fc00cfda529e@mail.gmail.com>
On Thu, Feb 18, 2010 at 3:12 PM, Adrian Tritschler <ajft@ajft.org> wrote:
> Flips in code are more likely to cause crashes, but still not
> guaranteed.
You'd need to look at fraction of total that is data vs. code, then at
fraction of total code that is going to cause hurt if flipped. This
stuff can have numbers attached.
Here's an example from my world. 1 MB of code, 32 MB of kernel, and
2GB minus that of data. This is a lower end ratio as the nodes don't
have much memory.
If the data is flipped, you're not going to know of errors unless you
are looking for numerical instability. People do.
And if you're in the middle of a checkpoint you won't know then.
But, this is all stuff that could be estimated ... and in some cases I
think has been.
ron
next prev parent reply other threads:[~2010-02-18 23:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:56 erik quanstrom
2010-02-18 18:26 ` matt
2010-02-18 18:31 ` ron minnich
2010-02-18 18:43 ` Patrick Kelly
2010-02-18 20:04 ` David Leimbach
2010-02-18 18:39 ` erik quanstrom
2010-02-18 20:46 ` ron minnich
2010-02-18 21:03 ` erik quanstrom
2010-02-18 21:14 ` Dave Eckhardt
2010-02-18 22:38 ` erik quanstrom
2010-02-18 23:08 ` roger peppe
2010-02-18 23:12 ` Adrian Tritschler
2010-02-18 23:27 ` ron minnich [this message]
2010-02-19 21:59 ` Dave Eckhardt
2010-02-20 22:17 ` erik quanstrom
2010-02-21 19:46 ` Dave Eckhardt
2010-03-05 10:01 ` hugh
2010-03-05 17:32 ` Dave Eckhardt
2010-02-18 18:43 ` Corey Thomasson
2010-03-08 17:57 ` Albert Skye
2010-03-08 19:06 ` erik quanstrom
2010-03-08 19:47 ` Jonas Amoson
2010-03-08 20:11 ` erik quanstrom
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=13426df11002181527tf091fbek49420d9a074614e7@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).