linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Chen, Gong" <gong.chen@linux.intel.com>
Cc: tony.luck@intel.com, m.chehab@samsung.com, rostedt@goodmis.org,
	linux-acpi@vger.kernel.org, arozansk@redhat.com
Subject: Re: [PATCH 1/5] trace, RAS: Add basic RAS trace event
Date: Wed, 16 Apr 2014 15:10:31 +0200	[thread overview]
Message-ID: <20140416131030.GC16741@pd.tnic> (raw)
In-Reply-To: <20140416063301.GC11297@gchen.bj.intel.com>

On Wed, Apr 16, 2014 at 02:33:01AM -0400, Chen, Gong wrote:
> On Wed, Apr 09, 2014 at 09:46:54PM +0200, Borislav Petkov wrote:
> > 
> > menuconfig RAS
> > 	bool "Reliability, Availability, Serviceability features"
> > 	help
> > 	  <A nice text about what this is going to contain, i.e. RAS stuff
> > 
> How about this:

Good. Just nitpicks below:

>          Reliability, availability, and serviceability (RAS) is a computer
>          hardware engineering term. Computers designed with higher levels
>          of RAS have a multitude of features that protect data integrity
>          and help them stay available for long periods of time without
>          failure.
> 
>          Reliability can be defined as the probability that it will produce

s/it/the system/. "it" is kinda misleading as to what we refer to.

>          correct outputs up to some given time. Reliability is enhanced by
>          features that help to avoid, detect and repair hardware faults.
> 
>          Availability is the probability a system is operational at a given
>          time, i.e. the amount of time a device is actually operating as the
>          percentage of total time it should be operating.
> 
>          Serviceability or maintainability is the simplicity and speed with
>          which a system can be repaired or maintained; if the time to repair
>          a failed system increases, then availability will decrease.

Nice!

>          Note that reliability and availability are distinct concepts:

capitalized: ... that Reliability and Availability are ...

>          Reliability is a measure of the ability of a system to function
>          correctly, including avoiding data corruption, whereas availability

ditto: Availability

>          measures how often it is available for use, even though it may not
>          be functioning correctly. For example, a server may run forever and
>          so have ideal availability, but may be unreliable, with frequent
>          data corruption.

Very good description! :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-04-16 13:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  5:52 Add new eMCA trace event interface Chen, Gong
2014-03-28  5:52 ` [PATCH 1/5] trace, RAS: Add basic RAS trace event Chen, Gong
2014-04-09 19:46   ` Borislav Petkov
2014-04-14  3:20     ` Chen, Gong
2014-04-14 10:46       ` Borislav Petkov
2014-04-16  6:33     ` Chen, Gong
2014-04-16 13:10       ` Borislav Petkov [this message]
2014-03-28  5:52 ` [PATCH 2/5] CPER: Adjust code flow of some functions Chen, Gong
2014-04-14 13:39   ` Borislav Petkov
2014-04-14 14:05     ` Borislav Petkov
2014-04-15  9:24       ` Chen, Gong
2014-04-15 18:02         ` Borislav Petkov
2014-04-16  5:01           ` Chen, Gong
2014-04-16 13:14             ` Borislav Petkov
2014-04-15  9:19     ` Chen, Gong
2014-04-15 18:05       ` Borislav Petkov
2014-04-16  6:23         ` Chen, Gong
2014-04-16 13:28           ` Borislav Petkov
2014-04-17  3:00             ` Chen, Gong
2014-03-28  5:52 ` [PATCH 3/5] trace, RAS: Add eMCA trace event interface Chen, Gong
2014-03-28  5:53 ` [PATCH 4/5] trace, eMCA: Add a knob to adjust where to save event log Chen, Gong
2014-04-03 23:46   ` Tony Luck
2014-04-04  8:05     ` Chen, Gong
2014-04-08  7:59     ` [PATCH 4/5 v2] " Chen, Gong
2014-03-28  5:53 ` [PATCH 5/5] trace, AER: Move trace into unified interface Chen, Gong

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=20140416131030.GC16741@pd.tnic \
    --to=bp@alien8.de \
    --cc=arozansk@redhat.com \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=rostedt@goodmis.org \
    --cc=tony.luck@intel.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 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).