How does Linux determine that some functionality should be classified as syscall while others can be directly implemented in user space?
How does Linux determine that some functionality should be classified as syscall while others
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How does Linux determine that some functionality should be classified as syscall while others can be directly implemented in user space?
A system call is performed when processing must occur in the Kernel – meaning that it requires escalated privileges or access to kernel-private resources. Typically if something can be kept in userspace, it’s done there. There could be performance reasons when things are moved to kernel processing, and therefore would require a system call to perform. Another facet is that the transition between userspace and kernelspace is relatively expensive.