From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,aef08d45f11a6d21
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.227.67 with SMTP id ry3mr2897819pbc.8.1340911233785;
        Thu, 28 Jun 2012 12:20:33 -0700 (PDT)
Path: 
 l9ni30569pbj.0!nntp.google.com!news1.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Newsgroups: comp.lang.ada
Subject: Re: max CPU load recommended
Date: Thu, 28 Jun 2012 22:20:31 +0300
Organization: Tidorum Ltd
Message-ID: <a53p3vFdaqU1@mid.individual.net>
References: <e1f284a7-6b1a-41c1-85e0-016cab6bc5c5@h9g2000yqi.googlegroups.com>
Mime-Version: 1.0
X-Trace: individual.net
 G9YA9x9sAV336y1XGXzlmQX/LmiK9n79xVyk/Lm4f19+3EP3Qvhxc3JE/A6aT6rTFR
Cancel-Lock: sha1:CJJ0DS3p5AZeeObKbH2T4BeVLdI=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:12.0) Gecko/20120428 Thunderbird/12.0.1
In-Reply-To: 
 <e1f284a7-6b1a-41c1-85e0-016cab6bc5c5@h9g2000yqi.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-06-28T22:20:31+03:00
List-Id: <comp.lang.ada>

On 12-06-25 12:53 , Gerd wrote:
> Sorry, this not an Ada related question, but maybe you could answer it
> best:
>
> What is a recommended value for maximum CPU load for safety systems?
> Are there any recommendations within 61508 or 26262?

I don't know what those standards recommend, but the idea of a "safe" 
CPU load is wrong, IMO. The actual CPU load varies with time; when the 
CPU is processing a task, its load is 100%; when it is waiting for some 
task to become ready, it is 0%. Any measured "CPU load" figure is an 
average over some time period and cannot be used to prove that the 
system meets its deadlines within that time period.

For example, if the system is expected to respond in 1 ms to an 
interrupt that occurs about twice per second, the average CPU load over 
one second can be quite small even if the response takes 10 ms instead 
of 1 ms.

You should rather compute the margins for all deadlines and put a limit 
there, for example 50% margin, or some absolute time margin.

Some rigorous schedulability analysis methods, like RMA, give predicted 
CPU loads and ensure that if this predicted load is below some limit 
then all deadlines will be met. Other (more flexible) analysis methods 
focus on response times rather than CPU loads.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .