1 |
> The mere fact you are asking/questioning with the term…. |
2 |
|
3 |
Well… sorry, I'm not asking :) As you probably can see, I'm trying to |
4 |
give some input of basic Scal@Grid assumptions and to hear some |
5 |
opinion back from people who believes they're men on this. |
6 |
|
7 |
I agree with your statements/terms above and RT as a science on the |
8 |
end – there is no magic or questions around - too much info is |
9 |
available from lots of universities, papers, researches, etc. |
10 |
And of course there is no question for FT and HA, techniques, |
11 |
approaches, methodologies, but... |
12 |
But let me please to continue in a different way. We will remove a |
13 |
science, a fault tolerance, HA and other thing that can confuse you, |
14 |
James (in advance – please be sure - I'm really happy that I found you |
15 |
and you can express your opinion on the subject) |
16 |
|
17 |
\\ |
18 |
So, we're considering some system that (we think so here) can |
19 |
guarantee (by some way that is not important at this step) meeting its |
20 |
deadlines with a given (by the operator) probability. It uses some |
21 |
techniques that adapts to the given (read - required) probability and |
22 |
actually proves that it achieves the requirement with the probability. |
23 |
Does it mean a system is a HRT? why/thoughts (?) |
24 |
|
25 |
We imply here that true HRT is impossible in reality and any single |
26 |
system that exists in the word meets hard real-time requirements with |
27 |
some probability. If it does not – HRT speaks of system failure. |
28 |
|
29 |
Please note, we speak of free programmable generic system here, |
30 |
something like a programmable logic microcontroller for custom |
31 |
application development. Any systems like DSP/matrix/etc are out of |
32 |
scope. |
33 |
|
34 |
-- |
35 |
gentoo-embedded@g.o mailing list |