Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

hardly a 100% solution (Developers)

posted by Ninho E-mail, 30.05.2011, 19:26

Passing by
>> Indeed
>> if some interrupt-activated resident chimes in after freeing but before
>> allocating, it could itself allocate from one or both of the blocks we've
>> just given back ! That would not be an error, as far as DOS is concerned,
...
> Yes, it does apply to my system. Yes, it could temporarily allocate memory
> in such a way as to prevent optimal allocation.

> However, as you said, that would not be an error (not just for DOS, in
> fact, it wouldn't be an error for anyone).

Not an error, but yes a failure due to a rude TSR not acting responsibly! Being able to preempt both the foreground task and the OS itself is a privilege, with privilege comes responsibility - at least I was brought up thinking so.

"Alternate method 1" sketched in my previous post, under CLI, would completely prevent the potential for such nuisance.

BTW just noticed the STI closing the critical section was unfortunately missing from the sample cut&pasted up thread. It should come precisely before section #7

---
Ninho

 

Complete thread:

Back to the forum
Board view  Mix view
22049 Postings in 2034 Threads, 396 registered users, 244 users online (0 registered, 244 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum