#Kernel Space vs. User Space?
6 messages · Page 1 of 1 (latest)
When your question is answered use !solved to mark the question as resolved.
Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question run !howto ask.
Typically kernel space programmers only work on the kernel itself
Say I want to read data from a file, eventually the program will have to find where the data for the file is on disk, resolve segmented data all that fun stuff. Basically the only program that directly interacts with the hardware is the kernel
How they sperate each other is by simply not allowing users to interact with the hardware directly, and instead they can only do so by going through the kernel
So for reading a file, the program sets up some data including the open file id, a pointer on where to write the data, and how much data to read, then you preform a system call.
At this point user space is exited, then the kernel picks up, does all the things it needs to do to complete the task, and user space returns
This question thread is being automatically closed. If your question is not answered feel free to bump the post or re-ask. Take a look at !howto ask for tips on improving your question.