304 views
0 votes
0 votes
When a user program makes a system call to read or write a disk file, it provides an indication of which file it wants, a pointer to the data buffer, and the count. Control is then transferred to the operating system, which calls the appropriate driver. Suppose that the driver starts the disk and terminates until an interrupt occurs. In the case of reading from the disk, obviously the caller will have to be blocked (because there are no data for it). What about the case of writing to the disk? Need the caller be blocked awaiting completion of the disk transfer?

Please log in or register to answer this question.

Related questions

0 votes
0 votes
0 answers
2
admin asked Oct 23, 2019
241 views
For each of the following system calls, give a condition that causes it to fail: fork, exec, and unlink.
0 votes
0 votes
0 answers
3
0 votes
0 votes
0 answers
4
admin asked Oct 23, 2019
219 views
To a programmer, a system call looks like any other call to a library procedure. Is it important that a programmer know which library procedures result in system calls? U...