| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Pre-emption under OS/2 |
Can someone give me a definitive answer as to how OS/2 handles scheduling in the following scenario: A low priority process (A) is scheduled and running A higher priority process (B) is blocked (probably on a com port) The process B becomes ready to run (by way of receiving a char) Question: Does process A get pre-empted immediately or does the scheduler wait until the slice allocated to process B has finished? My own experiments tend to indicate that OS/2 does *not* immediately pre-empt any low priority process when another higher priority process becomes ready to run. If this is the case then it's a major *pain* and results in a significant amount of wasted CPU time when running high-priority processes that are frequently blocked for just over one timeslice (which is not uncommon in some areas of development) --- Enigmax v1.04a* Origin: === Enigma BBS, Akld, NZ. +64 9 480-0951 === (3:772/350) SEEN-BY: 12/2442 54/54 620/243 622/407 623/630 624/50 632/339 348 640/715 820 SEEN-BY: 670/215 690/347 660 700/31 711/409 413 430 807 808 809 934 942 SEEN-BY: 712/353 414 623 713/888 770/115 771/1320 772/1 20 140 207 350 380 SEEN-BY: 774/605 800/1 @PATH: 772/350 20 712/353 711/409 54/54 711/808 809 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™.