| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: DosRead blocking |
On 13 Jan 97 08:55:43, Andrew Grillet scribed in letters of flame on the boiling sky: AG> I understood that DosEnterCritSec was just another name for AG> disable_interrupts. AG> Is that not the case? Agh! No! It stops switches to other threads *in that process*. Threads in other processes in the system run without interruption. (In fact they may run *faster* if you're doing something hefty in one of the threads blocked by DosEnterCritSec().) That said, it's an ugly hack because it stops *all* threads in the process, whether or not they are, or even could be doing anything related to the resource problem causing the critical section. And it can't cope with concurrency/contention problems on, for example, a shared memory buffer. ... Reality is for people who cannot cope with SF. --- Blue Wave/Max v2.30 [NR]* Origin: Me/2 (2:254/259) SEEN-BY: 50/99 54/99 270/101 620/243 625/160 711/401 413 430 934 712/311 407 SEEN-BY: 712/505 506 517 623 624 704 713/317 800/1 @PATH: 254/259 442/403 255/1 440/4 141/209 270/101 712/624 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.