Hi.... On Thu, Jun 17, 2010 at 23:30, Sudipta GHOSH <[email protected]> wrote: > Hi, > > Memory management , scheduling is part of core kernel. > > Is it a process or special code resides in RAM?
You can say, it's more like "event handler" > > As I see init process has PID 0, so the kernel code is a process or > special code. Not a process. Most of the times, kernel codes are handler...such as interrupt handler or exception handler or system call handler. The exception is codes that work inside kernel threads. > when there is an interrupt, device driver executes some code, in which > context? AFAIK, there are interrupt context, process context (other types maybe?) Process context itself is divided into: one that works on behalf of user mode process and the one that purely works in kernel mode. The example of the former is syscall handler, while the example of the latter is kernel thread > How data from userland to kernel space is transferred (user process to driver) You can use many methods: netlink, shared memory, direct memory access and so on. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
