operating system - Can a process terminate after I/O without returning to the CPU? -


i have question following diagram operating systems concepts: http://unboltingbinary.in/wp-content/uploads/2015/04/image028.jpg

this diagram seems imply after every i/o operation, process placed on ready queue before being sent cpu again. however, possible process terminate after i/o before being sent ready queue?

suppose have program computes number , writes storage. in case, process need return cpu after i/o operation? seems me process should allowed terminate right after i/o. way, there no need context switch.

once 1 process has executed termination request on another, threads of terminated process should never run again, no matter state in - blocked on i/o, blocked on inter-thread comms, running on core, sleeping, whatever - must stopped if running , put in state never run again.

anything else security issue - terminated threads should not given execution @ all, (else may not possible terminate process).


Comments

Post a Comment

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

im trying write component admin side , need add user creation. dont want duplicate existing codes add link. know how add task not simple link toolbar. thx help. if wanting button opens new user screen can try in component: $bar = jtoolbar::getinstance('toolbar'); $bar->appendbutton('link', 'users', 'new user','index.php?option=com_users&task=user.add'); you need add view.html.php file wherever you're creating toolbar. is need?
Read more

linux - disk space limitation when creating war file -

i have 1 gb disk space limitation hosting app , have used 700mb of it. however want create war file directory big (around 600mb) using command : jar -cvf root.war folderpath that's why encounter quota limitation , can't following. i'm looking way delete folder content when it's applying archive conserve disk space take note can't install zip tool in ssh shell ~ the code works on test directories, test first anyway, deletes files. it's not efficient. assumptions: 300mb free space, in destructively compress 600mb folderpath directory. none of files big -- if file in folderpath 300mb or larger, fail. notes: if ' $out ' file exists, nothing. first find pipes file list while , if ' $out ' doesn't exist in loop, create it, don't update -- if does exist, update it. each pass adds 1 more file, deletes unless file directory. after loop finishes delete empty directories too. unset u ; in=folderpath ; out=roo...
Read more