

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An overview of the minix system task, a kernel service that performs tasks for the file system (fs) and memory manager (mm) in csce 351 operating system kernels. The system task communicates with fs and mm via message passing ipc and is implemented as a device driver task. The purpose of the system task, its functions, and two specific messages: sys_copy and sys_trace.
Typology: Study notes
1 / 3
This page cannot be seen from the preview
Don't miss anything!


1
http://www.cse.unl.edu/~goddard/Courses/CSCE
u Perform kernel services for the File System (FS) and Memory Manager (MM) u Communicates with FS and MM via the standard message passing IPC u Implemented in Layer 2 (recall Fig 2-16) as a device driver task (line 14837 is start of sys_task) » Does not control an I/O device » Implements an interface to the internal system » Same privileges as I/O tasks and compiled in Kernel » Notice that it always sends a reply to the sender, even if the message request is invalid
3
u Figure 3-50, page 297, lists 19 types of messages that the System Task receives and processes u We will only talk about two (three) of these: » SYS_COPY (and SYS_VCOPY) v Most heavily used message. v Copies data to/from user processes for FS and MM » SYS_TRACE v Sent by MM v Supports PTRACE system call, which is used for debugging
u Used to move data from FS or MM space to user space u Required since FS and MM cannot directly access user process space u SYS_COPY implemented with do_copy, which simply calls phys_copy u SYS_VCOPY accepts multiple SYS_COPY requests as a single message to reduce overhead