<!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, Thomas Dörfler wrote:<br>
> Leon,<br>
><br>
> wouldn't it be better in that case to reaise your own priority beyond<br>
> all other tasks? This would make sure your task has the processor on its<br>
> own until it blocks (e.g. in an I/O operation).<br>
This is exactly the main goal I want to reach - to block all uncontrolled (by this task) I/O operations.<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>> When you suspend a bunch of tasks, you might even have to track, which<br>
> tasks already where suspended, to avoid that you resume a task that was<br>
> suspended by another piece of code...<br>
Hmmm... I thought that nested suspends are working... I mean, two suspends and one resume will leave task suspended....<br>
Isn't it correct?<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>> wkr,<br>
> Thomas.<br>
Many thanks<br>
Leon.</p></body></html>