You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to xos-dev...@googlegroups.com
1. What about having a release disk function as well inside the resource
manager module. The disk interrupt handler can invoke this function.
(There is some advantage to doing this - the disk interrupt handler have a
choice whether or not to wake up everyone waiting. This can be useful - for
example when the disk was acquired by the scheduler).
2. Documentation of resource acquisition order needs to be added. (The OS
does not 1. Preempt processes 2. Does hold and wait 3. There is mutual
exclusion. Hence the only condition that is avoidable is 4. circular wait. In
this case, the way to avoid circular wait is to put a sequence in which resource
requests will be made inside system calls. (So, that if process 1 requires resources
X and Y; process 2 requires X, Y then the request sequence will be the same in both
(say Y after X) so that we avoid the situation "1 holds X and 2 holds Y".
Dalton Fury
unread,
Oct 8, 2017, 12:55:35 AM10/8/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to xos-dev...@googlegroups.com
Sir,
1. This is good idea. We don't have to keep scheduling the idle process while swapping is in process? ie. all the processes waiting for disk will remain waiting for the disk until swapping is over.
2. Shall I start working on a draft? Can we add this to the Resource Manager page?