<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Console'; font-size:12pt; font-weight:400; font-style:normal;">On Wednesday April 22 2009, Manuel Coutinho wrote:<br>
> My 2 cents, if I may :) =><br>
><br>
> Why not make that task (that does the urgent job) with a high priority?<br>
> It seams the standard way of increasing responsiveness while allowing<br>
> interrupts and task switching…<br>
Because when, for example, doing I/O, the urgent task will allow task switching, and this will change the situation, which is unacceptable.<br>
The urgent task must process the "snapshot" of the moment it was started at.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Thanks.<br>
Leon<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Dr.Leon M.Pollak<br>
Director<br>
PLR Information Systems Ltd.<br>
Tel.:+972-98657670 | POB 8130, H'Aomanut 9,<br>
Fax.:+972-98657621 | Poleg Industrial Zone,<br>
Mob.:+972-544739246 | Netanya, 42160, Israel.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>